Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 3 May 2000 10:34:50 -0400
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: /cygdrive/windows ?
Message-ID: <20000503103449.F6787@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
References: <20000503005341 DOT B6109 AT cygnus DOT com> <NCBBIMLDAJGCPAFLLELBAEAKCHAA DOT espen DOT harlinn AT seamos DOT no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i
In-Reply-To: <NCBBIMLDAJGCPAFLLELBAEAKCHAA.espen.harlinn@seamos.no>; from espen.harlinn@seamos.no on Wed, May 03, 2000 at 12:06:47PM +0200

On Wed, May 03, 2000 at 12:06:47PM +0200, Espen Harlinn wrote:
>> On Tue, May 02, 2000 at 10:50:06PM -0400, DJ Delorie wrote:
>> >
>> >`cygpath --windir`
>> >
>> >The only time we'd need something like this visible outside a compiled
>> >application is a script, and a script can use cygpath to get the
>> >directory path and store it.  Any compiled program can just call
>> >GetWindowsDirectory() itself.
>>
>> Actually, I was thinking that it would be nice to have this in a tar file:
>>
>> /cygdrive/system/some.dll .
>>
>> This would always extract some.dll to the windows/system directory.
>
>IMHO: Putting things in windows\system[32] is not a very bright idea,
>keeping the complete cygwin installation in a separate directory is how I
>like it. At various times it has been usefull to have several different
>cygwin installations installed into different directories. If some.dll goes
>into windows\system[32] the requirement for backwards binary compability
>becomes more stringent when changes are made to some.dll. There is also the
>slight problem that some.dll may allready exist on the target system and it
>might just be something quite different from your some.dll i.e. a name
>clash.

Um.  I was not talking about putting cygwin stuff in windows/system.

I used the example "some.dll" not "cygwin1.dll".

cgf