X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ciem1NKYI7bcjPku
	EMa5+7MLfil68dy55QVGOWDNx2X/Lw8yQS178tt71s4EVEWirLhNpk/7WnoAbh1y
	jNnlqkKvl7sNrx+Fn8eWPDlZuzV1u0xZ0ynAH/4wrEgYeRkTk8Hehq4qJGZU7RFz
	en46dbV3MmD8naypgVBbmBCFcCE=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=sJ9RSn4lzXgBpFvl2/kZug
	gU4Xw=; b=LToNLtToLMRSXaMNF0XMH9B45Njl0wK8w0rsxllG/1dqDeD/gxuKTM
	3uxYhy05GylTPDch3BeVSUahuDnYGrGzLy77tDCdYxZ9m9TqsBy4FBSOb0+VZl7x
	Q8MpLs2GaNXDOVI4xNeu3Smz9QHylyJphB5VriCV3PxBowYV2oaqY=
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
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL autolearn=no version=3.3.1 spammy=icons, fstab, batch, elegant
X-HELO:	nsstlmta09p.bpe.bigpond.com
Subject:	Re: Possible Cygwin setup regression with --prune-install
To:	cygwin AT cygwin DOT com
References:	<158109b5-8d13-9e88-05b5-0eb581839e81 AT shaddybaddah DOT name> <87woewv79r DOT fsf AT Rainer DOT invalid>
From:	Shaddy Baddah <lithium-cygwin AT shaddybaddah DOT name>
Message-ID:	<b3bd95fc-d345-ffd9-a18d-102b62563e72@shaddybaddah.name>
Date:	Thu, 29 Aug 2019 16:52:25 +1000
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version:	1.0
In-Reply-To:	<87woewv79r.fsf@Rainer.invalid>
X-IsSubscribed:	yes

Hi Achim,

On 29/8/19 4:02 pm, Achim Gratz wrote:
> Shaddy Baddah writes:
>>   -Y --prune-install Prune the installation to only the requested
>> packages
>>
>> My reading of that is that this should defeat any packages from being
>> (automatically added). However, even with this option, the base packages
>> are still autoselected.
> 
> I've originally implemented that option and the Base packages and
> dependencies are explicitly exempted.  This is not an option to allow
> you to create broken installations, mind you.


But it's not an installation really. The only potential "breakage" that
I could see is that the attempt to create desktop icons would break.

But there's nothing to "postinstall", so having no shell, no anything
isn't an issue.

OK, I should expand a bit, to give some better understanding. For more
than a decade, I have employed an installation technique I'll call an
alternative root. See this for example:

https://sourceware.org/ml/cygwin/2009-07/msg00904.html

The setup allows me to have an install of Cygwin on a host system, and
reuse that in a guest VM, over the VM implementations shared FS. Much
like the concept of a "zone" in Unix, I setup in the guest an
alternative root, with its own etc, var, etc.. and of course fstab
for a /tmp away from the one with the limitations of the VM shared FS.

Before Cygwin 1.7, I achieved the alternative root through the registry
key. After Cygwin 1.7, I have maintained a local patch that works of an
environment variable to point at an "alternative root".

There are other non-VM applications to this too.

To bootstrap the "alternative root", I used to run setup as above. I
then could be sure that all the required directories under root were
created, with the right Windows ACL, etc.

I'd then fill in /etc, setup my launching batch file, and away I go.
It's worked very well for me for years.

I'd never expect the support of the list to continue this practice. I
just lament losing what I see as the "elegant" approach I had to
"bootstrap" the alternative root. I might look into maintaining another
local patch for Cygwin setup.

> 
>> But can someone talk to what --prune-install is exactly supposed to do?
>> And can any consideration be given to a "skeleton/template" install?
> 
> I use that option to make sure that whenever I remove packages from my
> install (or downgrade them), the clients pick the exact set of packages
> up that I give them.  It's also used to shrink installations (i.e. from
> a developer installation to user) without leaving lots of cruft behind.

Thank you for that. That is different to what I expected. And I can see
good uses for this option.

-- 
Regards,
Shaddy

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

- Raw text -