Avoid collisions between parallel installations of Cygwin

Corinna Vinschen corinna-cygwin@cygwin.com
Thu Oct 15 16:18:00 GMT 2009

On Oct 15 12:01, Christopher Faylor wrote:
> On Thu, Oct 15, 2009 at 11:43:33AM -0400, Christopher Faylor wrote:
> >On Thu, Oct 15, 2009 at 12:40:17PM +0200, Corinna Vinschen wrote:
> >>So, here's your next question:  Given that there are no or so few
> >>problem reports which could be tracked down to a MSYS/Cygwin
> >>co-existance problem, does that mean the potential problems are
> >>exaggerated, or does that mean we just didn't detect the cause of the
> >>problem?  As you can easily guess, I have no answer to this question.
> >
> >Since I'm about to leave on vacation, and don't want to hold anything
> >up, I won't have any objections to Corinna's changes if they include a
> >way for every running version of Cygwin to register itself and a way for
> >cygcheck to report the versions of Cygwin that have been run on the
> >system.  So, I that means an additional work in the DLL.  I don't think
> >it makes sense for anything other than cygwin1.dll to register itself
> >and I do understand that there may be issues with registry write
> >permissions.
> >
> >I saw Chuck's concerns about being able to turn off this behavior, and
> >it would be nice if they were addressed.
> It also occurs to me that some way to clean these things out of the
> registry would be nice.  Maybe cygcheck could optionally remove registry
> entries for nonexistent DLLs.


However, even if it would make my life easier to get this patch in ASAP,
it's not exactly necessary.  I will try to make this working in a way
which will satisfy all of us more or less, and then I'll send the resulting
patch to this list again.  I won't check anything related to this in
before you're back.

Have a nice vacation,

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