1.7.1 release date?

Corinna Vinschen corinna-cygwin@cygwin.com
Fri Dec 4 21:12:00 GMT 2009

On Dec  4 20:27, Corinna Vinschen wrote:
> On Dec  4 13:10, Christopher Faylor wrote:
> > I really don't like having things named incorrectly and, like I said,
> > having a directory named "release" which is really an old release and a
> > directory named "release-2" which is for Cygwin "1.7" is a recipe for
> > future confusion for me, at the very least, and, I think, for others
> > as well.
> I don't understand that.  If the need arises to have another release
> directory it will be called release-3, then release-4, etc.  There's
> nothing strange or puzzeling about that.
> Well, there is obviously no middle ground betwen the two points of view.
> If you really insist on the directory name, go ahead.  Just, please, do
> it over the weekend and keep me informed as soon as the change has been
> finished.

Here's one thing we should better not do, even if the directories get
renamed.  Please don't rename setup-2.ini to setup.ini.  It will result
in all sorts of broken installations if people decide to ignore the
"there's a new version of setup.exe" warnings, and I'm sure there are a
lot of people out there who ignore this message regulary, and are
neither subscribed to the cygwin list nor to the cygwin-announce list.
While you could easily say "their fault", I know that I'm doing that
once in a while as well, first pulling through the Cygwin package
updates, and just update to the new setup afterwards.  I'm sure there
are a lot of people doing that once in a while at least.  Updating to
the new release should better be a conscious decision on the user's

And that also shows a misconception I was stumbling over:  Of course
we don't need new setup.exe and setup-legacy.exe files if we just
rename the directories, since it's all in the ini files anyway.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-developers mailing list