0b1c5eda17
The property of removal overrides dropping out if the package was removed from the base layer felt a bit too magical and hacky. We really should remember that wish and re-apply it if the pkg comes back. This is similar to package layering: requests can become inactive (seems like a better word than "dormant") if the package is already part of the base layer, but they don't really go away. This patch reworks the logic so that removal overrides work the same way. In the status output, we now have both "RemovedBasePackages" and "InactiveBaseRemovals" (which is only printed in verbose mode), similarly to how we have "LayeredPackages" and "InactiveRequests". And similarly, we also print out in the upgrader during a transaction all the inactive base removals. Another cool thing is that we now allow any pattern to be specified at the CLI. E.g. `ex override remove /usr/bin/strace` will resolve to strace. Closes: #836 Approved by: cgwalters |
||
---|---|---|
.. | ||
fetch-journal.sh | ||
multitest.py | ||
overlay.sh | ||
sync.sh | ||
test-basic.sh | ||
test-initramfs.sh | ||
test-layering-basic.sh | ||
test-layering-gpg.sh | ||
test-layering-local.sh | ||
test-layering-non-root-caps.sh | ||
test-layering-relayer.sh | ||
test-layering-rpmdb.sh | ||
test-layering-scripts.sh | ||
test-layering-unified.sh | ||
test-livefs.sh | ||
test-override-remove.sh | ||
test.sh |