Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3B337A95.60102@ece.gatech.edu>
Date:	Fri, 22 Jun 2001 13:04:21 -0400
From:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1) Gecko/20010607 Netscape6/6.1b1
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
CC:	cygwin AT cygwin DOT com
Subject:	Re: [avail for test] readline-4.2-2
References:	<3B240A0F DOT F76676D1 AT ece DOT gatech DOT edu>

Charles S. Wilson wrote:

> I've just uploaded readline-4.2-2 as a test release.  Readline is a
> library that provides user-input functions complete with history
> functions and line-editing capabilities.  


Any objections if I remove the test designation from this release? 
4.2-2 contains both the old dll's (cygreadline4.dll and cyghistory4.dll) 
so that old .exe's will continue to work, and provides the new dll's 
(cygreadline4.2.dll and cyghistory4.2.dll) which newly linked programs 
will use. (The new dll's reflect the new 4.2 API, so it is possible that 
programs may require source code modification to link with the new 4.2 
libraries.)

Also, is cygreadline4.2.dll okay, or should I use a different 
nomenclature?  cygreadline4-2.dll?  cygreadline5.dll? (and break the 
relationship between dll version number and source package numbering).

I'm actually leaning toward cygreadline5.dll, since readline-4.3 may 
have the same API as 4.2, so the 4.3's dll may actually have to keep the 
4.2 package's dll name, and be called cygreadline4.2.dll which is VERY 
confusing.  If you just state, "DLL versioning has no relation to source 
package versioning" then it's okay that readline-4.2's dll and 
readline-4.3's dll are both "cygreadline5.dll".  So, it won't take much 
convincing for me to release readline-4.2-3 with a "cygreadline5.dll" 
instead of "cygreadline4.2.dll"...

One day, of course, libtool will work well with cygwin dll's, and many 
dll's will get renamed to something like cygfoo-2-3-1.dll using the 
libtool library versioning mechanism, I'm sure.  But that's WAY in the 
future. One thing at a time.

--Chuck



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -