public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Possible Cygwin setup regression with --prune-install
Date: Thu, 29 Aug 2019 06:52:00 -0000	[thread overview]
Message-ID: <87woewv79r.fsf@Rainer.invalid> (raw)
In-Reply-To: <158109b5-8d13-9e88-05b5-0eb581839e81@shaddybaddah.name> (Shaddy	Baddah's message of "Thu, 29 Aug 2019 14:48:10 +1000")

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 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.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

  reply	other threads:[~2019-08-29  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29  6:02 Shaddy Baddah
2019-08-29  6:52 ` Achim Gratz [this message]
2019-08-29  8:08   ` Shaddy Baddah
2019-08-29 15:34 ` szgyg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87woewv79r.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).