This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Add md5 checksum to snapshots?
- To: BINUTILS Patches <binutils at sourceware dot cygnus dot com>, newlib at sourceware dot cygnus dot com
- Subject: Add md5 checksum to snapshots?
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Tue, 04 Apr 2000 18:07:59 +1000
- CC: GDB Patches <gdb-patches at sourceware dot cygnus dot com>
- Organization: Cygnus Solutions
Hello,
The GDB snapshots now include an md5 checksum file (gdb-<release>/md5)
vis:
0636e73ff0215e8d672dc4c32c317bb3 COPYING
f30a9716ef3762e3467a2f62bf790f0a COPYING.LIB
a60b8cbed1f1909e5b22576752a3d06a Makefile.in
07c33a285703b40cd6f93a478e97e03b README
0636e73ff0215e8d672dc4c32c317bb3 bfd/COPYING
425357a8d33e0afc42b7b9c32508128f bfd/ChangeLog
.
.
.
The ``gdb-<version>'' prefix is omitted as it makes a mess of diffs)
Would the binutils + newlib groups be interested in having an equivalent
file included in their snapshots/releases? If so, I can update
src/Makefile.in so that it generates md5 checksums as part of the
archive process. The src/Makefile.in:taz target would be affected.
I could also always make the code conditional on ``MD5'' being defined.
enjoy,
Andrew