Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <01bf01c2f3ea$c8854830$cf6d86d9@ellixia> Reply-To: "Elfyn McBratney" From: "Elfyn McBratney" To: "cygwin" , "Andrew DeFaria" References: <200303261832 DOT 53052 DOT jld AT ecoscentric DOT com> <3E81FE8B DOT 9060008 AT Salira DOT com> <3E82101C DOT 45E8CBE7 AT isg DOT de> <3E82139B DOT 3020109 AT Salira DOT com> <00fd01c2f3df$01f5ae90$cf6d86d9 AT ellixia> <3E8228CE DOT 20208 AT Salira DOT com> Subject: Re: Determining the location of a Cygwin installation Date: Wed, 26 Mar 2003 22:55:22 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 > Elfyn McBratney wrote: > > >> While interesting there are two flaws here. Firstly, this down't work > >> on all versions of Windows. Secondly, if I could get my users to set > >> their "ApplicationPaths" I could as easily get them to set their > >> PATHs. The real world situation is that this is not the case and > >> neither PATH nore ApplicationPaths are set. > > > > So how about using something like regtool, there are quite a few > > native (non-Cygwin dependant) regtool alikes around. From there all > > you need to do is check HKLM or HKCU. Or write your own custom > > implementation. > > What exactly am I checking for? That ApplicationPaths is set properly or > that PATH has a Cygwin bin dir? And what if they don't. In that case I'm > back to the same situation in trying to determine where Cygwin was > installed. > > Or am I checking to see where Cygwin is installed by looking, as the > original poster had queried, where Cygwin's bin is mounted? How does > that fit with Christopher's assertion that that might go away? Again, I > would think it would be far more meaningful to dedicate at least one > registry spot to denote where Cygwin was installed and then build from > there. Seems to be a very logical way to do it from my point of view but > as always, this is just my opinion. Sorry, I wasn't too clear. :-) The latter is what I meant, and if Cygwin stops storing it's mount table in the registry setup.exe would have to know how to access/change it so maybe (I think you suggested it) a command line option would be best. This could show either a full or partial view of the mount table. Regards, Elfyn McBratney elfyn AT exposure DOT org DOT uk www.exposure.org.uk -- 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/