automake-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Automake-commit] [SCM] GNU Automake branch, ng/master, updated. v1.11-2


From: Stefano Lattarini
Subject: [Automake-commit] [SCM] GNU Automake branch, ng/master, updated. v1.11-2001-g2684923
Date: Sat, 18 Feb 2012 22:17:54 +0000

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 "GNU Automake".

http://git.sv.gnu.org/gitweb/?p=automake.git;a=commitdiff;h=268492330184c069d404aaad55a8ecb66458f576

The branch, ng/master has been updated
       via  268492330184c069d404aaad55a8ecb66458f576 (commit)
      from  ec08262650b5266cdb649f364283833192311c17 (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 -----------------------------------------------------------------
commit 268492330184c069d404aaad55a8ecb66458f576
Author: Stefano Lattarini <address@hidden>
Date:   Fri Feb 17 23:48:39 2012 +0100

    [ng] maint: downgrade version: 2.0a -> 0.5a
    
    Since Automake is still in the version series 1.x (at the moment of
    writing the last stable version being 1.11.3), labelling Automake-NG
    with a version of "2.0a" (as we've done in a recent commit) would
    mud the waters about what the "real" or "more recent" Automake is,
    and cause even more confusion about the Automake vs. Automake-NG
    distinction.  Which is precisely what we don't want.
    
    So let's downgrade the Automake-NG version to "0.5a".
    
    This change comes with a caveat of its own, though.
    
    After this "version downgrade", a project which requires a minimal
    Automake API version in AM_INIT_AUTOMAKE or AUTOMAKE_OPTIONS might
    get a "spurious" warning if someone tries to use Automake-NG to
    bootstrap it.  For example, a project whose configure.ac contains:
    
      AM_INIT_AUTOMAKE([1.10])
    
    would trigger a complaint from Automake-NG, since "1.10" is
    interpreted as a version number greater than "0.5a".
    
    Then again, while this is annoying right now, in the long run it
    might turn out to actually be helpful, in case we introduce some
    big or subtle backward-incompatibility between Automake-NG and
    mainstream Automake.
    
    Suggestion by Dave Hart.
    
    * configure.ac (AC_INIT): Change version number from 2.0a to 0.5a.

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

Summary of changes:
 configure.ac |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/configure.ac b/configure.ac
index 7c11411..62e44c1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -16,7 +16,7 @@
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
 
 AC_PREREQ([2.68])
-AC_INIT([GNU Automake-NG], [2.0a], address@hidden)
+AC_INIT([GNU Automake-NG], [0.5a], address@hidden)
 
 AC_CONFIG_SRCDIR([automake.in])
 AC_CONFIG_AUX_DIR([lib])


hooks/post-receive
-- 
GNU Automake



reply via email to

[Prev in Thread] Current Thread [Next in Thread]