This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[gcc_release] Add a comment to MD5SUMS
- From: Kelley Cook <kcook at gcc dot gnu dot org>
- To: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Cc: Gerald Pfeifer <gerald at pfeifer dot com>
- Date: Tue, 10 Aug 2004 16:35:44 -0400
- Subject: [gcc_release] Add a comment to MD5SUMS
- Hop-count: 1
This self-explanatory patch adds in a comment block to the top of
MD5SUMS for those that do not realize what function it provides.
OK?
BTW, the August 4th's GCC 3.3 snapshot actually ran, though no
indication of it made it to the GCC mailing list or gccadmin.
I think that mail to gcc.gnu.org may have been dropped for a period on
Wednesday afternoon as I attempted to mail a message to the list that
day at 20:00UTC which apparently went to the bitbucket.
2004-08-10 Kelley Cook <kcook@gcc.gnu.org>
* gcc_release (build_sources): Add comment header to generated MD5SUMS.
--- ../../gcc-orig/maintainer-scripts/gcc_release 2004-08-09 09:32:22.026742200 -0400
+++ gcc_release 2004-08-10 16:07:26.652055700 -0400
@@ -251,7 +251,17 @@ EOF
[ -f libcpp/po/cpplib.pot ] && mv ../objdir/libcpp/po/*.gmo libcpp/po/
# Create a "MD5SUMS" file to use for checking the validity of the release.
- find . -type f |sed -e 's:^\./::' -e '/MD5SUMS/d' |sort |xargs md5sum >MD5SUMS
+ echo \
+"# This is an MD5 Checksum of the GCC tarball.
+#
+# Besides verifying that all files in the tarball were correctly expanded, it
+# also can be used to determine if any files have changed since the tarball was
+# expanded or to verify that a patchfile was correctly applied.
+#
+# Suggested usage:
+# md5sum -c MD5SUMS | grep -v \"OK$\"
+" > MD5SUMS
+ find . -type f |sed -e 's:^\./::' -e '/MD5SUMS/d' |sort |xargs md5sum >>MD5SUMS
}
# Buid a single tarfile. The first argument is the name of the name