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 Date: Wed, 19 Mar 2003 20:22:17 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Bump version to 1.5.0 Message-ID: <20030320012217.GA32105@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20030319211947 DOT GA29068 AT redhat DOT com> <3E78E3DA DOT 7060408 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E78E3DA.7060408@yahoo.com> User-Agent: Mutt/1.5.1i 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). 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. cgf