Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton via Gdb-patches <gdb-patches@sourceware.org>
To: Andreas Schwab <schwab@suse.de>,
	Nick Clifton via Gdb-patches <gdb-patches@sourceware.org>
Cc: Binutils <binutils@sourceware.org>, Tzvetelin Katchov <katchov@gnu.org>
Subject: Re: RFC: Sort tarballs created by the src-release.sh script
Date: Thu, 29 Sep 2022 13:24:13 +0100	[thread overview]
Message-ID: <6a7c5183-a3a9-562f-6584-ed6306aee257@redhat.com> (raw)
In-Reply-To: <7927df56-70ca-64be-6ca8-023727e49383@redhat.com>

Hi Guys,

Thinking about this a little more last night, it occurred to me that if
we want reproducible tarballs then we should not be storing user names,
group names or modification times either. So what do you think about
this extended version of the patch:

diff --git a/src-release.sh b/src-release.sh
index 079b545ae7c..908492c28f7 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -185,8 +185,8 @@ do_tar()
      echo "==> Making $package-$ver.tar"
      rm -f $package-$ver.tar
      find $package-$ver -follow \( $CVS_NAMES \) -prune \
-       -o -type f -print \
-       | tar cTfh - $package-$ver.tar
+       -o -type f -print | LC_ALL=C sort \
+       | tar cTfh - $package-$ver.tar --mtime=0 --group=0 --owner=0
  }

  # Compress the output with bzip2


Cheers
   Nick


  reply	other threads:[~2022-09-29 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 12:59 Nick Clifton via Gdb-patches
2022-09-28 13:05 ` Andreas Schwab via Gdb-patches
2022-09-28 13:34   ` Nick Clifton via Gdb-patches
2022-09-29 12:24     ` Nick Clifton via Gdb-patches [this message]
2022-09-29 12:36       ` Jan Beulich via Gdb-patches
2022-09-30 11:38         ` Nick Clifton via Gdb-patches
2022-10-02  7:54           ` Sam James via Gdb-patches
2022-10-03  6:55             ` Jan Beulich via Gdb-patches
2022-10-03  6:59               ` Sam James via Gdb-patches
2022-10-03  7:41                 ` Andreas Schwab
2022-10-03 14:40               ` Nick Clifton via Gdb-patches
2022-10-03 19:56                 ` Andreas Schwab via Gdb-patches
2022-10-04  7:10                 ` Jan Beulich via Gdb-patches
2022-10-05 12:23                   ` Nick Clifton via Gdb-patches
2022-10-05 13:00                     ` Jan Beulich via Gdb-patches
2022-10-03  7:47             ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a7c5183-a3a9-562f-6584-ed6306aee257@redhat.com \
    --to=gdb-patches@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=katchov@gnu.org \
    --cc=nickc@redhat.com \
    --cc=schwab@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox