From: Gary V. Vaughan <gary@gnu.org>
Date: Tue, 26 Jan 1999 15:42:00 +0000 (+0000)
Subject: Damn me!!
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=87d1ce7865099462ba363055502fc1a3bc0cdf66;p=thirdparty%2Flibtool.git

Damn me!!
Looks like I have found a buglet in cvs.  For configure.in
we branched at revision 1.12, accidentally removed a line in
revision 1.13 and merged from HEAD to the branch.  Quite rightly
the removed line difference is applied to the branch during the
merge and is now missing from there too.  Now we put the line
back in the trunk for a new HEAD revision, but when we merge from
HEAD back to the branch for a second time, the line is *still*
missing from the branch.  The reason seems to be that cvs merge is
using the common ancestor (1.12) to find differences, and the
offending line is now present in the HEAD revision and the common
ancestor, so no difference there, so no change applied during the
merge onto the branch: net result the missing line is never put back.

I put it back by hand with this commit.  Grrrr.
---

diff --git a/configure.in b/configure.in
index e5280c80b..f9bb667ba 100644
--- a/configure.in
+++ b/configure.in
@@ -24,6 +24,7 @@ changequote([,])
     ;;
 esac    
 
+AC_SUBST(pkgdatadir)
 aclocaldir='${datadir}/aclocal'
 AC_SUBST(aclocaldir)