RFC: Sort tarballs created by the src-release.sh script

[Nick Clifton]

Hi Guys,

On 10/4/22 08:10, Jan Beulich wrote:
> Every commit should be considered to affect the tarball, imo, as such
> effects could also be indirect. If you really wanted to go that route,
> then perhaps an alternative would be to use the commit date of the
> most recent commit touching bfd/version.m4.

Hmm, except that would probably only be appropriate for binutils tarballs,
not others.

So how about the attached patch ?  This one adds a new command line option to
src-release.sh.  If it is not used then the behaviour is not changed in any
way.  If the new option is used, it provides a date that is passed to tar's
--mtime option, along with triggering the use of sort and the other tar
options necessary to make a reproducible tarball.  So:

   src-release.sh -x -r `git log -1 --format=%cd --date=format:%F bfd/version.m4` binutils

should create a pretty consistent tarball.

Cheers
   Nick


-------------- next part --------------
A non-text attachment was scrubbed...
Name: src-release.sh.patch
Type: text/x-patch
Size: 1656 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20221005/c47c6995/attachment.bin>