Document and automate signature creation for the release archives.
---
doc/manual/release.txt | 3 ++-
tools/release.sh | 9 ++++++++-
2 files changed, 10 insertions(+), 2 deletions(-)
Document and automate signature creation for the release archives.
---
doc/manual/release.txt | 3 ++-
tools/release.sh | 9 ++++++++-
2 files changed, 10 insertions(+), 2 deletions(-)
======
diff -u tools/release.sh tools/release.sh
--- tools/release.sh (working copy)
+++ tools/release.sh (working copy)
@@ -262,7 +262,14 @@
echo "Staging package archives:"
mkdir -p archives
for EXT in tar.gz tar.bz2 zip; do
- mv -v "${PACKAGE_RELEASE}.${EXT}" archives/
+ local FILE="${PACKAGE_RELEASE}.${EXT}"
+ # create archive signatures
+ for HASH in md5 sha1; do
+ echo "sign: ${FILE}.${HASH}"
+ ${HASH}sum "${FILE}" > "archives/${FILE}.${HASH}"
+ done
+ # save archive
+ mv -v "${FILE}" archives/
done
cp -a NEWS archives/
cp -a ChangeLog archives/
only in patch2:
unchanged:
--- doc/manual/release.txt (revision 2757)
+++ doc/manual/release.txt (working copy)
@@ -224,10 +224,11 @@
-# Produce the package source archives:
-# Start with a clean working copy, used for producing releases only.
-# Switch to release tag branch: svn switch .../${RELEASE_TAG}
- -# produce a ChangeLog for the release (using svn2cl).
+ -# Produce a ChangeLog for the release (using svn2cl).
-# @c bootstrap, @c configure, and @c make the package.
-# Run <code>make distcheck</code> to produce the distribution archives.
-# Run <code>make maintainer-clean</code> verify the repository is empty.
+ -# Create signature files using md5sum, sha1sum, etc.
-# Publish documentation for the release:
- Allow users to access the documentation for each of our releases.
- Place static copies of the following files on the project website:
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
