[Top][All Lists]

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

FYI: 57-gary-really-force-version-timestamps.patch

From: Gary V. Vaughan
Subject: FYI: 57-gary-really-force-version-timestamps.patch
Date: Wed, 26 Nov 2003 15:42:32 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925 Thunderbird/0.3

Applied to HEAD.
Gary V. Vaughan      ())_.  address@hidden,}
Research Scientist   ( '/
GNU Hacker           / )=
Technical Author   `(_~)_
Index: ChangeLog
from  Gary V. Vaughan  <address@hidden>
        Okay, the problem I am trying to solve is that when a change (say,
        bumping the version to 1.6 for the next release) is committed, the
        timestamp in ChangeLog is updated, but and libtoolize
        inherit the pre-commit build number from config.status.  This
        delta notes the change in build number in the unstamped ChangeLog
        and forces a rerun of configure etc. to roll a new with
        the correct TIMESTAMP:

        * (stamp-vcl): We actually need a new config.status to
        force the correct timestamp into libtoolize and,
        rerunning autoconf has no effect at all if hasn't

2003-11-26  Gary V. Vaughan  <address@hidden>

RCS file: /cvsroot/libtool/libtool/,v
retrieving revision 1.85
diff -u -p -u -r1.85
--- 26 Nov 2003 13:36:31 -0000 1.85
+++ 26 Nov 2003 15:35:46 -0000
@@ -50,9 +50,9 @@ libtoolize: $(srcdir)/ $(to
        chmod +x $@
-# Make sure configure is regenerated when the version timestamp changes
-$(top_builddir)/config.status: stamp-vcl $(top_srcdir)/ChangeLog
-stamp-vcl: vcl.tmp
+# Make sure config.status is regenerated when the version timestamp changes
+$(config_status): stamp-vcl
+stamp-vcl: vcl.tmp $(top_srcdir)/ChangeLog
        @set `$(SHELL) config/mkstamp < $(top_srcdir)/ChangeLog`; \
        echo "$$1" > vcl.tmp

Attachment: pgp8aT4t60f3N.pgp
Description: PGP signature

reply via email to

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