[rtems-source-builder commit] 5: Update Newlib

[Chris Johns]

On 6/6/19 3:04 pm, Sebastian Huber wrote:
> On 06/06/2019 02:23, Chris Johns wrote:
>> On 5/6/19 10:16 pm, Sebastian Huber wrote:
>>> +tools/rtems-gcc-fb371a33fa6-newlib-5c2a3661c
>> Is there a timetable for gcc 7 branch releases? I see the built gcc executable
>> clearly shows the version of gcc is 7.4.1 which is great so I am wondering if
>> this file name would be clearer if the branch was included, ie
>> `tools/rtems-gcc-7.4-fb371a33fa6-newlib-5c2a3661c`. I am not concerned with
>> newlib as much because there are no branches like we have with gcc.
>>
>> I raise this because I saw `rtems-gcc-fb371a33fa6-newlib-1d35a003f` being built
>> by the RSB and I did not know if this was master, a branch or which branch. Also
>> the package name is the name of the source tarball and so the name used in a
>> release on our ftp servers.
> 
> We could use the branch number and atimestamp for the files, e.g.
> 
> rtems-gcc-fb371a33fa6-newlib-5c2a3661c ->
> rtems-gcc-7-2019-06-05-newlib-2019-06-05
> 

I am not sure what "for the files" means?

I am fine with the git hash being present. It does make it easy find the history
given a tarball.

All I think we need is the branch added to the package name and the source
tarball. What we currently see is:

package: powerpc-rtems5-gcc-fb371a33fa6-newlib-1d35a003f-x86_64-apple-darwin18.5.0-1

Chris