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: <011301c0ebf4$31b61ce0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>, <cygwin AT sources DOT redhat DOT com>
References: <3B19D318 DOT C71AAD1C AT ece DOT gatech DOT edu>
Subject: Re: [avail for test] readline-4.2-1
Date: Sun, 3 Jun 2001 16:12:30 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 03 Jun 2001 06:03:55.0859 (UTC) FILETIME=[F9012A30:01C0EBF2]

----- Original Message -----
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
To: <cygwin AT sources DOT redhat DOT com>
Sent: Sunday, June 03, 2001 4:03 PM
Subject: [avail for test] readline-4.2-1


> I've just uploaded readline-4.2-1 as a test release.  Readline is a
> library that provides user-input functions complete with history
> functions and line-editing capabilities.
>
> readline-4.2-1 depends on ncurses-5.2-5.
>
> WARNING: Chet Ramey, the maintainer of the GNU readline package, has
> changed the readline API between version 4.1 and 4.2.  Some functions
SNIP
> Therefore, the DLL version in this package is "4.2" instead of "4".
> That way, binaries that depend on the old dll (like postgresql) can
> coexist with the new package.
>
> HOWEVER!!! Setup will *uninstall* the old dll when upgrading readline.
SNIP

I think this is the first time this has occured with the new setup.

If I can make a suggestion: would it make sense to have 2 readline
packages, one with the old binary, and one with the new binary? If the
headers collide, then that might not be trivial, but you could make the
old readline package be libraries only.

Other projects/platforms do this quite routinely when a package breaks
backward compatability, keeping both in production until no packages
need the old binary.

Rob


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