setup: uninstalling an orphaned package
Mon Mar 26 17:55:00 GMT 2018
In ChooserPage::applyCommandLinePackageSelection() we have the following
bool wanted = pkg.isManuallyWanted();
bool deleted = pkg.isManuallyDeleted();
bool basemisc = (pkg.categories.find ("Base") !=
|| pkg.categories.find ("Orphaned") != pkg.categories.end ());
bool reinstall = (wanted || basemisc) && deleted;
One strange consequence of this is that if the user tries to uninstall
an orphaned package on the command line, then setup will instead try to
This behavior was introduced in the following commit:
Author: Corinna Vinschen <email@example.com>
Date: Thu Jul 25 12:03:49 2013 +0000
Uninstalled packages in categories "Base" or "Misc" are always selected
for installation; installed packages in these categories are not
eligible for deletion and will be reinstalled or upgraded instead.
I can't understand the rationale for this. Did "Misc" (which has since
been renamed to "Orphaned") used to have a different meaning?
I found it very surprising when I tried to uninstall a bunch of packages
in unattended mode, and setup failed with download errors because it
tried to reinstall orphaned packages.
More information about the Cygwin-apps