Updated: libtool-devel-1.5, libltdl3-1

[Charles Wilson]

Max Bowsher wrote:
> Ongoing development has stabilized the devel version, but there is still
> call for 2 sets of autotools. Now "devel" = "current" and "stable" =
> "legacy", legacy being for those projects still using ac-2.13.
> 
> However, renaming the Cygwin autotool packages is probably more effort than
> it is worth.

What he said.

The devel branch of libtool on cygwin will now be numbered using a 
1.5.x-y numbering scheme, where 1.5.x is the official libtool release 
upon which our cygwin version is based.  The -y represents the cygwin 
release version, and may also indicate that additional patches were 
applied.  These patches may be "original" (e.g. from me), or they may be 
pulled from libtool's CVS as necessary.

We lose specific "CVS date" information, but now that we FINALLY have a 
usable official release for cygwin -- after 2.5 years of waiting -- I 
want to stick as closely as possible to official source, and not use 
extra patches or CVS stuff.  As much as possible.

So, to refect this, I've shifted the numbering scheme for libtool-devel 
from "CVS checkout date" to 1.5.x.

But, we still need a "stable" (or legacy) branch for the autotools, and 
a "devel" (or current) branch.  And this will be true for a long time -- 
until most packages that USE libtool have officially updated to use the 
current versions (libtool-1.5.x, AM-1.7.x, AC-2.5x).  At some point in 
the distant future, we may want to move what we currently call "-devel" 
into the "-stable" tree, and adopt ??? libtool-2.0, AM-2.0, AC-3.0 ??? 
as the -devel tree.

Or maybe not.  Maybe -- at that distant time -- the tools will have 
progressed to the point that you can have multiple installed versions 
without these stupid scripts and "switching" frameworks.  Who knows?

But I don't see ANY of that happening for at least two years.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/