This is the mail archive of the
binutils-cvs@sourceware.org
mailing list for the binutils project.
[binutils-gdb] Add a warning to the how-to-make-a-release notes to check the permissions on the files in the tarbal
- From: Nick Clifton <nickc at sourceware dot org>
- To: bfd-cvs at sourceware dot org
- Date: 18 Oct 2017 13:40:47 -0000
- Subject: [binutils-gdb] Add a warning to the how-to-make-a-release notes to check the permissions on the files in the tarbal
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8071ec0990927fd747483ffaad3b5d3b16355643
commit 8071ec0990927fd747483ffaad3b5d3b16355643
Author: Nick Clifton <nickc@redhat.com>
Date: Wed Oct 18 14:40:06 2017 +0100
Add a warning to the how-to-make-a-release notes to check the permissions on the files in the tarball.
* README-how-to-make-a-release: A note about checking file and
directory permissions.
Diff:
---
binutils/ChangeLog | 5 ++++-
binutils/README-how-to-make-a-release | 17 +++++++++++++----
2 files changed, 17 insertions(+), 5 deletions(-)
diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index 016c376..89359bd 100644
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,6 +1,9 @@
2017-10-18 Nick Clifton <nickc@redhat.com>
- * MAINTAINERS: Moev Svein Seldal to Past Maintainers section.
+ * README-how-to-make-a-release: A note about checking file and
+ directory permissions.
+
+ * MAINTAINERS: Move Svein Seldal to Past Maintainers section.
2017-10-18 Alan Modra <amodra@gmail.com>
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index c87f27e..2f65989 100644
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -58,11 +58,20 @@ looks like this:
[optional: add "-u XXXXX" to sign with a gpg key]
git push origin binutils-2_XX_X
- f. Create the release tarballs:
+ f. Check that your file creation mask will create the
+ correct file permissions. Eg:
+
+ umask 022
+
+ g. Create the release tarballs:
./src-release -b -g -l -x binutils
- g. Edit bfd/development.sh and set "development=true".
- h. Commit this change into the git repository.
- i. Clean up the source tree. (Use "git status" to find new
+
+ h. Check that the files in the tarballs have the correct
+ permissions.
+
+ i. Edit bfd/development.sh and set "development=true".
+ j. Commit this change into the git repository.
+ k. Clean up the source tree. (Use "git status" to find new
files, and remove them).
FIXME: The tarballs will contain spurious autom4te.cache