public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Subject: Re: Question regarding min reqd dejagnu version
Date: Tue, 4 Oct 2022 10:52:23 +0100	[thread overview]
Message-ID: <92cab149-dd27-43ff-f6e6-da0e9e9d29fc@redhat.com> (raw)
In-Reply-To: <41d734aa-50bb-2868-0ed4-e40941b5776d@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 311 bytes --]

Hi Guys,

   I am checking in the attached patch to update the README-maintainer-mode
   file so that it also lists a minimum version of dejagnu required to run
   the testsuites.  Whilst I was at it I noticed that the URLs needed a https:
   prefix rather than ftp:, so I changed that as well.

Cheers
   Nick

[-- Attachment #2: maintainer-mode.patch --]
[-- Type: text/x-patch, Size: 2107 bytes --]

diff --git a/README-maintainer-mode b/README-maintainer-mode
index 6d65d289c8e..fdafa692c0c 100644
--- a/README-maintainer-mode
+++ b/README-maintainer-mode
@@ -5,10 +5,10 @@ Note that if you configure with --enable-maintainer-mode, you will need
 special versions of automake, autoconf, libtool and gettext. You will
 find the sources for these in the respective upstream directories:
 
-  ftp://ftp.gnu.org/gnu/autoconf
-  ftp://ftp.gnu.org/gnu/automake
-  ftp://ftp.gnu.org/gnu/libtool
-  ftp://ftp.gnu.org/gnu/gettext
+  https://ftp.gnu.org/gnu/autoconf
+  https://ftp.gnu.org/gnu/automake
+  https://ftp.gnu.org/gnu/libtool
+  https://ftp.gnu.org/gnu/gettext
 
 The required versions of the tools for this tree are:
 
@@ -24,3 +24,12 @@ Makefiles in the parent directories before running the Makefiles in
 the child directories.  There is no easy way around this (short of
 changing the automake macros) as these dependencies need to exist in
 order to correctly build the NLS files.
+
+When running the testsuites a minimum version of dejagnu is also needed.
+Dejagnu can be found here:
+
+  https://ftp.gnu.org/gnu/dejagnu/
+
+The minimum version required is:
+
+  dejagnu 1.5.3
diff --git a/src-release.sh b/src-release.sh
index 079b545ae7c..de1f98a70bb 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -184,9 +184,15 @@ do_tar()
     ver=$2
     echo "==> Making $package-$ver.tar"
     rm -f $package-$ver.tar
+    # The sort command and --mtime, --group and --owner options are
+    # used in order to create consistent, reproducible tarballs.
+    # BUILD_DATE is set to SOURCE_DATE_EPOCH if defined, or the
+    # modification date of this file otherwise.  cf:
+    # https://reproducible-builds.org/docs/source-date-epoch/
+    BUILD_DATE="$(date --utc --date="@${SOURCE_DATE_EPOCH:-$(date -r src-release.sh +%s)}" +%Y-%m-%d)"
     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=$BUILD_DATE --group=0 --owner=0
 }
 
 # Compress the output with bzip2

  reply	other threads:[~2022-10-04  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01  0:18 Indu Bhagat
2022-10-03 10:23 ` Nick Clifton
2022-10-03 17:55   ` Indu Bhagat
2022-10-04  9:52     ` Nick Clifton [this message]
2022-10-04 10:05       ` Jan Beulich
2022-10-04 10:20         ` Nick Clifton
2022-10-04 10:27           ` Jan Beulich
2022-10-04 11:40             ` Nick Clifton
2022-10-05 18:28               ` Indu Bhagat

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=92cab149-dd27-43ff-f6e6-da0e9e9d29fc@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).