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: <3E78E3DA.7060408@yahoo.com> Date: Wed, 19 Mar 2003 16:40:42 -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> In-Reply-To: <20030319211947.GA29068@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 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. Christopher Faylor wrote: > > I know that we'd talked about changing to version 2 of cygwin, too, but > that is going to be a pretty daunting task. It means someone amongst us > would have to write a cygwin1 wrapper DLL so as to not leave the old > cygwin1 users behind. It ideally means rebuilding the whole > distribution with cygwin2 libraries. It means stripping out all of the > legacy code in cygwin1.dll (rewarding as that would be). >