apr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gst...@apache.org
Subject cvs commit: apr-dist/tools release.sh
Date Wed, 28 Aug 2002 09:50:38 GMT
gstein      2002/08/28 02:50:38

  Modified:    tools    release.sh
  Log:
  Don't allow a release of a tag which hasn't been declared as a formal
  release. If developers want to make a tarball from another tag, then
  they can simply edit this script.
  
  Also fixed up the header comment.
  
  Revision  Changes    Path
  1.2       +11 -1     apr-dist/tools/release.sh
  
  Index: release.sh
  ===================================================================
  RCS file: /home/cvs/apr-dist/tools/release.sh,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- release.sh	28 Aug 2002 00:52:37 -0000	1.1
  +++ release.sh	28 Aug 2002 09:50:38 -0000	1.2
  @@ -2,7 +2,7 @@
   #
   # release.sh : build a release tarball
   #
  -# USAGE: release.sh VERSION
  +# USAGE: release.sh VERSION [SIGNING-USER]
   #
   #   The version number is specified as MAJOR.MINOR.PATCH (and will be used
   #   in the output tarball name). The script will then look for a CVS tag
  @@ -11,6 +11,9 @@
   #   to prepare and construct the tarball. The subdirectory will be cleaned
   #   up upon exit.
   #
  +#   The "signing user" is the name of the key that you'll be signing the
  +#   release with.
  +#
   
   if test "$#" != 1 && test "$#" != 2; then
     echo "USAGE: $0 VERSION [SIGNING-USER]"
  @@ -50,6 +53,13 @@
   
   echo $split
   echo ""
  +
  +if grep '#define.*APR_IS_DEV_VERSION' ${dirname}/include/apr_version.h > /dev/null;
then
  +  echo "ERROR: apr_version.h still defines a development version. This"
  +  echo "       script can only produce formal releases."
  +  exit 1
  +fi
  +
   echo "Eliminating unwanted files (e.g. .cvsignore) and generating initial"
   echo "files via buildconf ..."
   echo ""
  
  
  

Mime
View raw message