#17208: libtool update to 2.2.6a ------------------------------------+--------------------------------------- Reporter: nox@macports.org | Owner: boeyms@macports.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: Resolution: | Keywords: Port: libtool libtool-devel | ------------------------------------+--------------------------------------- Comment(by boeyms@macports.org): Replying to [comment:2 nox@…]:
http://www.gnu.org/software/libtool/news.html
Despite a new and improved M4 interface to Libtool from Autoconf, every effort has been made to retain backwards compatibility with the 1.5.x interfaces. Autoupdate (which ships with Autoconf) will help you upgrade your configure.ac to the new interface when you are ready to migrate.
So even if it does break a port, it will be easy to fix the `configure.ac` script.
That's fine for those releasing libtool-based software, but it sounds to me like we would have to run autoupdate and then autoconf on every libtool-based port that libtool-2.x breaks, which would add new build time dependencies (which hopefully can be removed later, but that depends on the upstream developers). That also assumes that it would work every time -- if not, we'd have to write patches to fix it as well. I can tell you that libtool-2.2 broke building libxslt for me, while staying with libtool-1.5.6 worked fine, but that was almost 6 months ago now, I didn't know about autoupdate then, and that was the only port that I tested, so I can't give any indication of how many of our ports would break, or how easy fixing by using autoupdate would be. Personally, I've been thinking of having a "libtool1" for use with ports that break, and for "libtool" to keep tracking the latest stable version; that way, all we'd have to do to fix broken ports would be to change the dependency from libtool to libtool1. That assumes, however, that libtool-1.x and libtool-2.x can be installed together, and I can't remember whether or not they can. (In addition, I've been wondering whether or not we should create "libtool2" anyway for ports that need it now, with a view to making life easier if and when libtool goes to 3.x.) What does everyone else think? -- Ticket URL: <http://trac.macports.org/ticket/17208#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS