RTEMS 4.11.2-rc3 Release

[Chris Johns]

On 10/04/2017 07:02, Joel Sherrill wrote:
> On Apr 9, 2017 3:59 PM, "Needell, Jerry" <Jerry.Needell at unh.edu
> <mailto:Jerry.Needell at unh.edu>> wrote:
>
>     Joel,
>     Thats just what I am seeing. RC1 worked fine for me as well.
>     When the build gets to rtems-tools  for RC3 it still seems to be
>     looking in :
>
>     ...releases/4.11/4.11.2-rc3
>     rather than
>     ...releases/4.11/rc/4.11.2-rc3
>
>     Maybe I’m not imagining this …. ;-)
>
> No you are not.  :)
>
> Chris will wake up soon so should answer shortly. I could manually
> download rtems-tools but I don't think that's useful at this point.
> Looks like an rc4 is needed.

The problem is due to these lines:

https://git.rtems.org/rtems-source-builder/tree/rtems/config/tools/rtems-tools-1.cfg#n28
https://git.rtems.org/rtems-source-builder/tree/rtems/config/tools/rtems-kernel-4-1.cfg#n67

The `%define without_release_url` was added to the config file because 
the tools and kernel source are not located in the `sources` directory, 
they are in the release's top level directory.

Removing `%define without_release_url` does not help because we get the 
error from the source not being found in `sources` directory.

I think the best solution is to remove the `%define without_release_url` 
from the tools and kernel configuration files plus the explicit paths 
and update the release scripts to have the tools and kernel source in 
the `sources` directory and the release's top level directory. This 
means the "release-url" is consistent in all use cases and I can remove 
the path hack in the configuration files.

The release's top level directory is just the RTEMS source packages and 
I think having a second copy is a minor overhead.

I have reopened #2952.

Chris