[Nmh-commits] [SCM] The nmh Mail Handling System branch, master, updated. 0287c2e441fbc748cb11f96a5afd6dbdf68b0818

[Ken Hornstein]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The nmh Mail Handling System".

The branch, master has been updated
       via  0287c2e441fbc748cb11f96a5afd6dbdf68b0818 (commit)
       via  e6d71f88fe62d7508ccd1809cd7e822bbb116b00 (commit)
      from  0d86c4af58df9a6361d12bc25cdfba30c4983868 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.savannah.gnu.org/cgit/nmh.git/commit/?id=0287c2e441fbc748cb11f96a5afd6dbdf68b0818


commit 0287c2e441fbc748cb11f96a5afd6dbdf68b0818
Author: Ken Hornstein <address@hidden>
Date:   Mon Feb 6 10:27:43 2012 -0500

    Update the developer documentation with the changes to the release
    process.

diff --git a/docs/README.developers b/docs/README.developers
index cba9f46..3876ba6 100644
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -136,67 +136,50 @@ getpass()    nmh_getpass()
 releasing nmh
 -------------
 
-To make a public release of nmh (we'll use version 1.0.4 and my mhost.com
+To make a public release of nmh (we'll use version 1.5 and my mhost.com
 account, danh, as examples here; the convention for release candidates
-is to use something like "1.0.4-RC1"):
+is to use something like "1.5-RC1"):
 
- 1. % echo 1.0.4 > VERSION
+ 1. % echo 1.5 > VERSION
     % date +"%e %B %Y" > DATE
     (DATE should contain something like "30 December 2000")
 
  2. % git commit VERSION DATE; git push
 
- 3. % git tag -a nmh-1_0_4 -m 'Releasing nmh-1_0_4.'
+ 3. % git tag -a 1.5 -m 'Releasing nmh-1.5.'
 
- 4. % make nmhdist
+    Note that the new convention for tagging is to simply tag with the
+    version number (tag formats in the past have varied).
 
- 5. Untar nmh-1.0.4.tar.gz and `diff -r' it vs. your workspace.  Make
-    sure no files got left out of the distribution that should be in
-    it (due to someone forgetting to update the DIST variables in the
-    Makefiles).
+ 4. % make distcheck
 
- 6. If you have root access on your machine, it's good at this point to do:
+    If you want to check the distribution build with some particular
+    configure options, set the DISTCHECK_CONFIGURE_FLAGS variable.
+    E.g.:
 
-    % chown -R 0:0 nmh-1.0.4
-    % tar cvf nmh-1.0.4.tar nmh-1.0.4
-    % gzip nmh-1.0.4.tar
+    % make distcheck DISTCHECK_CONFIGURE_FLAGS=--with-cyrus-sasl
 
-    If you leave the files in the archive as being owned by yourself, your UID
-    may coincide with one of a user on a machine where nmh is being installed,
-    making it possible for that user to Trojan the nmh code before the system
-    administrator finishes installing it.
-
- 7. Make sure your new tarball uncompresses and untars with no problem.  Make
-    sure you can configure, make, and install nmh from it.
-
- 8. If all is well and your tarball is final, go back to your workspace and do:
+ 5. If all is well and your tarball is final, go back to your workspace and do:
 
     % echo 1.0.4+dev > VERSION
 
- 9. % git commit VERSION; git push
-
-10. If possible, make an MD5 hash and/or a PGP signature of nmh-1.0.4.tar.gz.
-    Assuming you have gpg set up, this should be:
-    % gpg --output nmh-1.0.4.tar.gz.sig --detach-sig nmh-1.0.4.tar.gz
+ 6. % git commit VERSION; git push
 
-    You can verify the signature with
-    % gpg --verify nmh-1.0.4.tar.gz.sig nmh-1.0.4.tar.gz
+ 7. Upload the distribution file to savannah.  You can automate this process
+    by doing:
 
-11. Upload the files to savannah. First make sure they are mode 664 so
-    they will have the right permissions on the server end
-    (see https://savannah.gnu.org/maintenance/SharedDownloadArea)
-    % chmod 664 nmh-1.0.4.tar.gz*
+    % make upload SAVANNAH_USERNAME=username
 
-    Then scp them across:
-    % scp -p nmh-1.0.4.tar.gz* address@hidden:/releases/nmh/
+    This will automatically call gpg to sign the release.  You can bypass
+    this step by setting the SKIP_GPG_SIG variable.
 
-12. Update the http://www.nongnu.org/nmh/ homepage. (It lives in the CVS
+ 8. Update the http://www.nongnu.org/nmh/ homepage. (It lives in the CVS
     'webpages repository'; see https://savannah.nongnu.org/cvs/?group=nmh)
 
-13. Add a news item to the savannah nmh page. You'll have to submit it first
+ 9. Add a news item to the savannah nmh page. You'll have to submit it first
     and then separately approve it (under News->Manage).
 
-14. Send the release announcement email to the following places:
+10. Send the release announcement email to the following places:
      address@hidden
      address@hidden
      address@hidden

http://git.savannah.gnu.org/cgit/nmh.git/commit/?id=e6d71f88fe62d7508ccd1809cd7e822bbb116b00


commit e6d71f88fe62d7508ccd1809cd7e822bbb116b00
Author: Ken Hornstein <address@hidden>
Date:   Mon Feb 6 09:08:19 2012 -0500

    More configure cleanup to modern constructs.

diff --git a/configure.ac b/configure.ac
index 70832a8..10da4b3 100644
--- a/configure.ac
+++ b/configure.ac
@@ -52,34 +52,25 @@ dnl Do you want client-side support for using SASL for 
authentication?
 dnl Note that this code will be enabled for both POP and SMTP
 AC_ARG_WITH([cyrus-sasl], AS_HELP_STRING([--with-cyrus-sasl],
   [Enable SASL support via the Cyrus SASL library]))
-if test x"$with_cyrus_sasl" != x -a x"$with_cyrus_sasl" != x"no"; then
-  AC_DEFINE([CYRUS_SASL], [1],
-    [Define to use the Cyrus SASL library for authentication of POP and 
SMTP.])dnl
-  if test x"$with_cyrus_sasl" != xyes; then
-    AC_MSG_WARN([Arguments to --with-cyrus-sasl now ignored])
-    AC_MSG_WARN([Please pass the appropriate arguments to CPPFLAGS/LDFLAGS])
-  fi
-  sasl_support=yes
-else
-  sasl_support=no
-fi
+AS_IF([test x"$with_cyrus_sasl" != x -a x"$with_cyrus_sasl" != x"no"],[
+      AC_DEFINE([CYRUS_SASL], [1],
+               [Define to use the Cyrus SASL library for authentication of POP 
and SMTP.])dnl
+      AS_IF([test x"$with_cyrus_sasl" != xyes],[
+           AC_MSG_WARN([Arguments to --with-cyrus-sasl now ignored])
+           AC_MSG_WARN([Please pass the appropriate arguments to 
CPPFLAGS/LDFLAGS])])
+      sasl_support=yes], [sasl_support=no])
 
 dnl Do you want client-side support for encryption with TLS?
 AC_ARG_WITH([tls], AS_HELP_STRING([--with-tls], [Enable TLS support]))
-if test x"$with_tls" != x -a x"$with_tls" != x"no"; then
-  AC_DEFINE([TLS_SUPPORT], [1], [Support TLS for session encryption.])dnl
-  tls_support=yes
-else
-  tls_support=no
-fi
+AS_IF([test x"$with_tls" != x -a x"$with_tls" != x"no"],[
+      AC_DEFINE([TLS_SUPPORT], [1], [Support TLS for session encryption.])dnl
+      tls_support=yes],[tls_support=no])
 
 dnl What should be the default editor?
 AC_ARG_WITH([editor],
   AS_HELP_STRING([--with-editor=EDITOR],[specify the default editor]))
 
-if test -n "$with_editor"; then
-  editorpath="$with_editor"
-fi
+AS_IF([test -n "$with_editor"], [editorpath="$with_editor"])
 
 dnl Set the backup prefix
 AC_ARG_WITH([hash-backup],
@@ -323,9 +314,7 @@ AC_PATH_PROG([vipath], [vi], [/bin/vi], [$pathtmp])
 
 dnl If editor is not specified yet,
 dnl then use `vi' as the default.
-if test -z "$editorpath"; then
-  editorpath="$vipath"
-fi
+AS_IF([test -z "$editorpath"], [editorpath="$vipath"])
 AC_SUBST([editorpath])dnl
 
 dnl ----------------------------------------------------------

-----------------------------------------------------------------------

Summary of changes:
 configure.ac           |   35 +++++++++------------------
 docs/README.developers |   59 +++++++++++++++++------------------------------
 2 files changed, 33 insertions(+), 61 deletions(-)


hooks/post-receive
-- 
The nmh Mail Handling System