X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Message-ID: <4A0EB9B5.6030406@byu.net> Date: Sat, 16 May 2009 07:03:49 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: libtool, how should the version be parsed? References: <4A0E37F6 DOT 10109 AT cwilson DOT fastmail DOT fm> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to René Berber on 5/15/2009 10:16 PM: > $ libtoolize --version | sed 's/^[^0-9]*\([0-9].[0-9.]*\).*/\1/' > 1.3081 > 2003 > > 2009 > ... > > Weird, its looking for the first number, must be as confused as I am, So that should be reported as a bug in the package parsing the version numbers. > I > can understand if something is version X and part of say coreutils > version Y, but libtool X being part of "GNU libtool" Y? libtool 1.3081 comes from ChangeLog entry 3081; the libtool authors wanted to have a monotonically increasing number in every development build (not present in formal release builds) to make it easier to track exactly _which_ development build you are using. The package number, 2.2.7a, is only bumped for formal releases, with odd letters (aceg...) designating development alpha snapshots, even letters (bdfh...) designating betas, and the absence of a letter being a stable release. True, cygwin is a bit unusual for using a development snapshot, rather than a formal release, of libtool, but that's because there hasn't yet been a formal release containing the latest round of patches necessary for use on cygwin. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoOubUACgkQ84KuGfSFAYBZ4wCgjOBp8WNs1W09HY6QR9RhHyNn KyIAn0mlzwuk3Db8XxZl39ESYbehA4G7 =UPce -----END PGP SIGNATURE----- -- 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/