new stable 2.2 branch has been almost entirely rewritten -thanks
I'm following upstream discussions about this, but won't put it in Rawhide until we freeze for F9 as it might break quite a few packages. Same for libtool-1.5.26 even though I don't expect any major breakages caused by it.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
BuZapp wrote: > Changing version to '9'... Just don't do that.
(Adding keyword FutureFeature to denote this.)
changing back to rawhide as that's where futurefeatures live
Are we still planning to do this for F10 ? If yes, please don't wait until shortly before beta...
Re: comment #6: not very likely. I've started a mass rebuild on my system and got a huge amount of build failures caused by the new libtool. Not because of real bugs in libtool, but because of minor incompabilities, obsoleted functions and so on. I think I'd rather build a libtool2 package than replace libtool-1.5 with this new version.
Thats fine with me too. Will _that_ happen sometime soon, then ?
Libtool 2.2.4 is required to build freetype (2.3.8pre) from CVS. But not for releases as far as I can tell. One incompatibility is that --install flag needs to be passed to obtain some of the behavior of the old tool.
Karsten, any motion on this ? It is getting increasingly complicated to handle e.g. doing upstream releases on Fedora systems without running into gotchas due to libtool version differences with other distros...
(In reply to comment #10) > Karsten, any motion on this ? > > It is getting increasingly complicated to handle e.g. doing upstream releases > on Fedora systems without running into gotchas due to libtool version > differences with other distros... Perhaps a wiki page listing the packages that don't work with libtool 2.x would get the cooperation of the maintainers of those packages?
(In reply to comment #11) > (In reply to comment #10) > > Karsten, any motion on this ? > > > > It is getting increasingly complicated to handle e.g. doing upstream releases > > on Fedora systems without running into gotchas due to libtool version > > differences with other distros... > > Perhaps a wiki page listing the packages that don't work with libtool 2.x would > get the cooperation of the maintainers of those packages? I am the maintainer of some packages like that. But I have a hard time fixing them up for libtool 2.x until that libtool version becomes available in Fedora. Unless you want me to switch to some other distro for my upstream development needs, that is...
anyone up for a package review ? bugzilla #459387
There are at least a couple popular distros that have ported to libtool 2.2. Maybe we can borrow their patches en masse?
Things didn't look too bad in my latest mass rebuilds. There were ~100 new build failures introduced by switching from libtool-1.5 to libtool-2.2.6a, this looks quite doable. I've put the build logs of those build attempts on http://karsten.fedorapeople.org/libtool2-failures/