This is the mail archive of the
mailing list for the Cygwin project.
Re: Avoid collisions between parallel installations of Cygwin
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 15 Oct 2009 13:27:30 -0400
- Subject: Re: Avoid collisions between parallel installations of Cygwin
- References: <4AD74F95.firstname.lastname@example.org>
- Reply-to: cygwin-developers at cygwin dot com
On Thu, Oct 15, 2009 at 12:36:37PM -0400, Charles Wilson wrote:
>> On Thu, Oct 15, 2009 at 06:17:33PM +0200, Corinna Vinschen wrote:
>>>On Oct 15 16:03, Earnie Boyd wrote:
>>>> Quoting Corinna Vinschen <email@example.com>:
>>>>> Does it hurt? No. There's only one such entry per installation path.
>>>>> Your thumb drive, typically using the same drive letter every time
>>>>> it's used on a machine, will result in one entry.
>>>> Too bad. Really I want to leave zero dust when the thumb drive is removed.
>>>No way, right now, given the "Program Options". I think the trade-off
>>>of adding a single entry to the registry to know a path were a DLL has
>>>been installed once is worth its money if it helps to track down
>>>potential problems in the long run. It's just one grain of dust in the
>>>big picture ;)
>> As Chuck said, this is an argument for being able to tune the DLL itself
>> via the resource section or whereever. But I don't think it's something
>> that must go in 1.7.1.
>Certainly not. We might think about addressing all of the registry
>'grains' at once, later on (but I believe 'Program Options' are treated
>specially by windows itself; there may not be anything we can do to
>achieve the current behavior seen with a non-empty Program Options key
>[*], /without/ actually using Program Options).
>[*] on my system, the Program Options key is empty for all of my various
>cygwin installations, both in HKCU and HKLM
Program Options is supposed to be filled in by the user so that's no