X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49965DBB.6070505@tlinx.org>
Date: Fri, 13 Feb 2009 21:59:23 -0800
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: RFE: CygWinDir in ENV
References: <4990B031 DOT 4050807 AT tlinx DOT org> <4990B128 DOT 7030004 AT cygwin DOT com>   <4990CB8D DOT 3050704 AT tlinx DOT org> <4990D05A DOT 4050202 AT cygwin DOT com> <4990DA52 DOT 9050900 AT tlinx DOT org>   <4990E0BF DOT 1010502 AT cygwin DOT com> <4990EC89 DOT 8070901 AT tlinx DOT org>  <4991004F DOT 1080006 AT cygwin DOT com>  <4991E1CC DOT 9060804 AT tlinx DOT org>  <Pine DOT NEB DOT 4 DOT 64 DOT 0902101450530 DOT 21431 AT panix1 DOT panix DOT com> <4991EB3C DOT 3090800 AT cygwin DOT com> <Pine DOT NEB DOT 4 DOT 64 DOT 0902101617520 DOT 3221 AT panix2 DOT panix DOT com> <49920C32 DOT 7050507 AT cygwin DOT com>
In-Reply-To: <49920C32.7050507@cygwin.com>
X-Stationery: 0.4.8.12
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Larry Hall (Cygwin) wrote:
> Tim McDaniel wrote:
>> You did mention
>>
>> ] HKLM/Software/Cygwin/setup, the "rootdir" value.
>>
>> But you noted that that is in version 1.7.
> 
> This would work for 1.5 as well if someone back-ported the 1.7 change.
---
	Several shell scripts are called by setup, but I'm
not familiar with when they are called or their ordering.
	But for the programs run from setup -- if CYGWINDIR
was set in "setup.exe"'s environment, wouldn't that propagate it
to any child processes it started?
	If that's the case, then either
a) if it already calls a post-install script
   or
b) could call a post-install script,

AND if it could pass HKLM or HKCU (for all-user vs. current user
install) to the script as an arg, the script could just call
the windows 'exe' with 'add' to just add the key to the  HKCU as an
arg (for all-user vs. current user install and the script could
use the that to call the reg command. to add the key and to the
global or CU location.

But this presumes setup calls any scripts after setup and can pass
an argument and that it can set the correct value in the environment
before calling any other installation binaries or scripts.

	I've never had any joy in getting cygwin or setup to build
on my past systems nor my current system.  I can build other packages
on linux, (kernel, perl, squid, samba, bash, linux, perl, squid and
smaller packages from their tarballs or rpms), but when it comes
to cygwin or setup.exe...  I have always ended up with missing tools,
header files, link files, missing linked systems, wrong version
libraries...whatever...  always something.

	I think there is some base set of assumptions that are so
simple and normal to each of the communicators (giver/receiver) that
neither is aware they exist, let alone able to document or 'verbalize'
them as being necessary preconditions.

	The 'setx.exe' tool mentioned by Lee would be great but for
one minor problem.  It's not on most people's system.

	It's included in the Win 2k, and WinXP (and I presume Vista)
"Support Tools" or "Release Kit" packages.  While I think they are
'free' (past their EULA), I doubt they would be redistributable by a
3rd party.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/