Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <20000626153743.15312.qmail@web115.yahoomail.com> Date: Mon, 26 Jun 2000 08:37:43 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: Introducing slight binary incompatibility in newer executables? To: DJ Delorie Cc: cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- DJ Delorie wrote: > > > IMHO, it is, any cygwin-app that is updated now, will have to have > > the updated cygwin1.dll. What other changes are you thinking of? > > We bump the middle number when the converse is true - when updating > the DLL means you *must* update the cygwin apps also. > > All we're doing with this change is the same thing we've been doing > with all our other changes - adding functionality. This means that > apps built for the new DLL won't work with older DLLs. > > If we change or remove functionality, *then* we bump the middle > number, because apps build for the old DLL won't work with the new > DLL. It's only when backward compatibility is broken do we have to > worry about migration. Ok. But, IMO, we need a 1.1.4 before this modification so that we can take advantage of Corinna's patches for the speed issues of ntsec. Then 1.1.5 will contain this modification. Regards, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/