Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3B19D7C2.62C1FC9D@ece.gatech.edu> Date: Sun, 03 Jun 2001 02:22:58 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Collins CC: cygwin AT sources DOT redhat DOT com Subject: Re: [avail for test] readline-4.2-1 References: <3B19D318 DOT C71AAD1C AT ece DOT gatech DOT edu> <011301c0ebf4$31b61ce0$0200a8c0 AT lifelesswks> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Robert Collins wrote: > Charles Wilson wrote: > > 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. No, setup always uninstalls the previous package before installing the new one. That's what the installed.db file and the /etc/setup/readline.lst.gz file are used for. There are sneaky ways around this (a little thought and a peek at the setup.exe source would reveal them) but simple saving the old dll's is much simpler than the sneaky stuff. > 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. Yes, that would make sense, in a commercial distribution. However, what you're really asking is for me to add another package to the list of those I maintain. I already have too many. I will not add another. Cygwin-net is not a commercial distribution, and I am a volunteer with severly limited time (having just finished my Ph.D. proposal I am now "ABD" -- All But Dissertation -- and *really* must cut back my cygwin time). > Other projects/platforms do this quite routinely when a package breaks > backward compatability, keeping both in production until no packages > need the old binary. Yes, that is true. In this case, the ONLY package the needs the old binary is postgresql. The new readline is a test release. I will try to coordinate with Jason so that both postgres and readline are updated together (e.g. if possible, I will refrain from promoting this "test" version of readline to "official" status until Jason is ready to release a corresponding postgres). --Chuck -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple