Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <ADeFaria AT Salira DOT com>
Subject: Re: Determining the location of a Cygwin installation
Date: Wed, 26 Mar 2003 12:51:31 -0800
Lines: 33
Message-ID: <3E8212D3.5070004@Salira.com>
References: <200303261832 DOT 53052 DOT jld AT ecoscentric DOT com> <NCEBJJFMCAOKNNABBFIMIEBLDFAA DOT john DOT r DOT morrison AT ntlworld DOT com> <b5stct$gjq$1 AT main DOT gmane DOT org> <3E81FE8B DOT 9060008 AT Salira DOT com> <00ab01c2f3d4$e9b05920$cf6d86d9 AT ellixia> <3E820C43 DOT 8080400 AT Salira DOT com> <20030326203818 DOT GB3487 AT tortuga DOT etc DOT sk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT main DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en, ru, zh

Marcel Telka wrote:

> On Wed, Mar 26, 2003 at 12:23:31PM -0800, Andrew DeFaria wrote:
>
>> Elfyn McBratney wrote:
>>
>>> But as cgf (the Really Cool Manager) said the registry keys are not 
>>> to be relied on as they might not be there forever.
>>
>> Yeah but what I'm saying is that there should be a commitment to at 
>> least one registry entry which denotes the [active] installation path of
>
> This goal could be reached by adding the directory into the PATH. If 
> this is not done be default using setup.exe (which is not), then you 
> could add it by hand... I don't see any problem with this.

Let me describe a problem scenerio (real world).

You have a bunch of people in your domain who rely on Cygwin but who do 
not always keep up with the latest. Indeed often they are way behind. 
These people do not bother to add Cygwin's bin directory to their PATH 
either. A problem crops up and they call you. So you investigate and 
think that perhaps updating their Cygwin to a relatively recent version 
would correct their problem. So you do that. Then you think "Gee, 
wouldn't it be nice if I could keep everybody's Cygwin up to some 
relatively recent (and stable) version..." and you attempt to scriptize 
this. The first road block you hit is trying to determine where the user 
installed Cygwin - some in C:\Cygwin, others in D:\Cygwin and still 
others in some other odd path. Now what do you to?

(Of course, going hand in hand with this would be a command line driven 
setup.exe but perhaps we shouldn't go there just yet...)



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/