Date: Sun, 15 Dec 2002 14:25:25 -0500 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: "James E. Flemer" <jflemer@acm.jhu.edu>, "AlanE" <alane@geeksrus.net> Cc: <freebsd-ports@FreeBSD.ORG> Subject: Re: libtool 1.3 and 1.4 Message-ID: <019401c2a470$395d3f60$1200a8c0@gsicomp.on.ca> References: <Pine.LNX.4.33L2.0212151314110.8012-100000@centaur.acm.jhu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sun, 15 Dec 2002, AlanE wrote: > > > On Sat, Dec 14, 2002 at 07:58:09PM -0500, James E. Flemer wrote: > > > > --snip-- > > > > > >I took a few hours today to review the patches offered by > > >Jeremy, and to look at the way concurrent versions of > > >autoconf (et al) are handled in ports. As a result, I > > >threw together a revised set of patches that may be enough > > >to get things moving towards a happy coexistence of both > > >versions of libtool in the ports tree. Attempts were made > > >to keep as many existing ports from breaking, but some > > >cases could not be avoided. > > > > I'll take a look at this. The basic ground rules for doing this are that > > nothing may change in the way automake and autoconf are handled in > > bsd.port.mk, all non-current versions install info files with version in > > name, all non-current versions create a libexec/thingNNN/thing-program > > link to the real binary, and person supplying the patches fixes every > > port that breaks as a result of the patch. > > I did not change any auto* bits (intentionally). > Libtool13 installs: (among others) > info/libtool13.info > libexec/libtool13/libtool -> bin/libtool13 > libexec/libtool13/libtoolize -> bin/libtoolize13 > > I guess the question is which version would be "current" > and which would be "non-current". I would like to see > FreeBSD move to 1.4 as current; it has to happen sometime, > and more and more programs want 1.4 to build. As you > mentioned when ports are thawed there is going to be > breakage all over the place, so it may be a good time to > shake things up with libtool. As Alan and I have discussed in the past, the move to libtool-1.4 will break *everything*, since the ltconfig script doesn't exist anymore -- it's been replaced by some m4 script. This means that every port that uses libtool will need USE_AUTOCONF in order to generate a configure file and libtool script that takes into account our FreeBSD mods instead of the GNU default assumptions. Of course, this can't be done without the appropriate logic in bsd.port.mk, and Alan had asked me to hold off on my 1.4 patches until we release 5.0-RELEASE and get the support for autoconf / automake cleaned up. Only then is the time right to start looking at getting libtool-1.4 integrated into the ports system. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?019401c2a470$395d3f60$1200a8c0>