DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3B554385DDC6
To: Stromeko AT nexgo DOT de
Cc: cygwin AT cygwin DOT com
Subject: Re: setup: --prune-install appears to be broken
In-Reply-To: <87le2z5xv7.fsf@>
Date: Tue, 25 Jun 2024 11:55:09 -0300
Message-ID: <8734p18436.fsf@gmail.com>
MIME-Version: 1.0
Precedence: list
From: David McFarland via Cygwin <cygwin AT cygwin DOT com>
Reply-To: David McFarland <corngood AT gmail DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>


> You are misunderstanding what prune-install does: it ensures that only
> the exact list of groups/packages that you give it for installation
> (plus their dependencies) is installed when it finishes and you
> literally said you want to end up with no packages at all.

That's not what it's doing though. When run on an empty root, it
installs Base (the set of packages in category "Base"), and when run
again, it does nothing (i.e. leaves Base installed'), even if other
packages were installed.

I actually think what it _should_ do is leave Base installed, by
treating all Base packages as implicitly referenced:

      bool uninstall = (!(wanted  || base) && (deleted || PruneInstallOption))

So we uninstall packages if they are neither wanted nor Base, and either
explicitly deleted or --prune-install.

However, the bigger problem is that none of this is actually working,
because of that "Can't happen.  No packagemeta for base" error.

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