Re: Introducing slight binary incompatibility in newer executables?

[Earnie Boyd <earnie_boyd at yahoo dot com>]

--- DJ Delorie <dj@delorie.com> 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: <mailto:earnie_boyd@yahoo.com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/