Avoid collisions between parallel installations of Cygwin

Corinna Vinschen corinna-cygwin@cygwin.com
Mon Oct 12 19:28:00 GMT 2009

On Oct 12 14:53, Charles Wilson wrote:
> Corinna wrote:
> > Here are the questions.
> > - Does anything speak against the idea of the patch?
> > - Does anybody see a problem with the patch?
> > - Anything else?
> I think it's great. I have found it SO useful to have both a cygwin-1.5
> and a cygwin-1.7 tree installed (e.g. when I break my 1.7 tree I can fix
> it using familiar cygwin tools from the 1.5 installation, rather than
> cmd.exe or explorer) -- and I've been able to do that because the
> 1.5/1.7 versions *mostly* don't interfere.
> comments about the patch:
> cygwin/external.cc [CW_GET_INSTKEY]: it's dangerous to rely on the
> fall-thru behavior to 'default: break;' if somebody adds another case.
> Use an explicit break; statement.

Gargh!  Thanks for catching, I'll fix it right away.  Looking into
cygwin_internal() it seems this isn't the first time...

> cygwin/shared.cc: The first big comment block appears incomplete: "Thus,
> different Cygwin installations generate different object names and so
> are"....are what?

Hmm, looks like I lost track while writing this.  I don't know anymore
what I was trying to say, but you can expect something like "...
isolated from each other." or something.

> Should cygcheck be modified to print out the installation_key?

That sounds like a good idea.  It could be helpful to diagnose the 3PP
problems which will never happen again (cough, cough).


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