X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org CB134385783D
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=dronecode.org.uk
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=jon DOT turney AT dronecode DOT org DOT uk
Authentication-Results:	btinternet.com;
	auth=pass (PLAIN) smtp.auth=jonturney AT btinternet DOT com
X-Originating-IP:	[86.158.32.120]
X-OWM-Source-IP:	86.158.32.120 (GB)
X-OWM-Env-Sender:	jonturney AT btinternet DOT com
X-VadeSecure-score:	verdict=clean score=0/300, class=clean
X-RazorGate-Vade:	gggruggvucftvghtrhhoucdtuddrgeduiedrudegjedgkeduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhuffvfhfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpeekueffueeutdehhfejtdevheevieekheetjeekjedthefhteetheehkedvgeeuudenucfkphepkeeirdduheekrdefvddruddvtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrudduudgnpdhinhgvthepkeeirdduheekrdefvddruddvtddpmhgrihhlfhhrohhmpeeojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhequceuqfffjgepkeeukffvoffkoffgpdhrtghpthhtohepoegthihgfihinhestgihghifihhnrdgtohhmqedprhgtphhtthhopeeothhhvghmihifihesghhmrghilhdrtghomheq
X-RazorGate-Vade-Verdict:	clean 0
X-RazorGate-Vade-Classification:	clean
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Subject:	Re: Forcing setup.exe not to create WSL symlinks
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<CAALQ5rnxo0_pJqTo5+617sZ6NPyDEuw5LkK_w5tMihYnTRfHrg AT mail DOT gmail DOT com>
	<875z95tg5c DOT fsf AT Rainer DOT invalid>
	<1f4a80f7-0e14-1641-3fce-317ac2a6dd00 AT dronecode DOT org DOT uk>
	<CAALQ5rnsexseL=gNd5VKkZSi2=Feg4vFLFGG8OmFcmVhyKvWoQ AT mail DOT gmail DOT com>
	<20200827090010 DOT GZ3272 AT calimero DOT vinschen DOT de>
	<CAALQ5rmB41AaANP6n3GNWbO4zLUjSyuuJ+2WwS=PWNqWbp7hXA AT mail DOT gmail DOT com>
	<CAALQ5rn5=oqGOge7mTFGoDeJCxD6H4=cFN3Mww+My4DMxNPsEQ AT mail DOT gmail DOT com>
Message-ID:	<cbeb8d61-e725-dabf-7883-352649adeb28@dronecode.org.uk>
Date:	Sun, 6 Sep 2020 15:44:02 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.12.0
MIME-Version:	1.0
In-Reply-To:	<CAALQ5rn5=oqGOge7mTFGoDeJCxD6H4=cFN3Mww+My4DMxNPsEQ@mail.gmail.com>
X-Spam-Status:	No, score=-6.1 required=5.0 tests=BAYES_00, FORGED_SPF_HELO,
	KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_NONE,
	TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On 27/08/2020 13:48, Michael Wild via Cygwin wrote:
> Hmm, OK, changing script.cc to not strip out CYGWIN is trivial. But the
> harder part is that main.cc uses ShellExecuteEx() with
> SHELLEXECUTEINFO.verb set to "runas" in order to re-run setup elevated.
> This resets all environment variables back to default. In my instance I can
> circumvent this by passing --no-admin and running from an elevated shell
> where CYGWIN is set already. And indeed, this works and resolves my Docker
> problem. I attached this fix as a patch. But on the other hand, I find this
> behavior to be a bit confusing. However, I don't see an easy way of
> resolving the "runas" issue, because it is by design. An option would be
> that the calling process passes the CYGWIN variable as a command line
> argument to the elevated process. But that is also ugly. What do you guys
> think?

I think an option which explicitly specifies the symlink style would be 
best (rather than option to specify the CYGWIN env var).

You'd also need to teach setup to create syminks in these different 
ways, and set the CYGWIN env var for scripts appropriately.
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -