Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3E79B303.8060608@yahoo.com> Date: Thu, 20 Mar 2003 07:24:35 -0500 From: Earnie Boyd Reply-To: cygwin-developers AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-developers AT cygwin DOT com Subject: Re: Bump version to 1.5.0 References: <20030319211947 DOT GA29068 AT redhat DOT com> <3E78E3DA DOT 7060408 AT yahoo DOT com> <20030320012217 DOT GA32105 AT redhat DOT com> In-Reply-To: <20030320012217.GA32105@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > On Wed, Mar 19, 2003 at 04:40:42PM -0500, Earnie Boyd wrote: > >>FYI, I bootstrapped msys tools by modifying the cygwin1.dll in the >>binary executable. So, it's conceivable to postinstall a sed script >>that would modify the dll name with caveats of new functionality not >>supported. > > > I used to do this all of the time in B19 days back when the DLL name > changed with each release. That's changed now. It was quite a battle > to get it changed, too (cgf bows). > Clap, clap, clap ... loud applause. :) Yes, it was a good thing. > The problem in this scenario is that just about every structure has changed > now. stat, FILE, passwd, etc. Changing the name of the DLL will just cause > most executables to crash. > I think I realized this after typing and pressing send. But what about > I can also see the possibility for 32/64 bit versions for each new > release with 32bit versions using libcygwin1.a while 64bit versions > using libcygwin2.a. An arbitrary date would be set to remove support > for a 32bit versions. Earnie.