Summary: | quickpkg --include-config=y breaks config file protection | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Dave Armstrong <dave0x01> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | ago, tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dave Armstrong
2013-04-05 01:25:09 UTC
I don't see any convenient way to protect against this kind of problem. The same kind of problem also prevents quickpkg --include-unmodified-config from knowing if a config file was modified by a user prior to a previous quickpkg/install cycle (that's why it's disabled be default, just like --include-config is). We can add warnings about these behaviors to the documentation for both options. I think that would be good enough. Because of quickpkg's inherent flaws, I would advise people to avoid using it whenever possible, and to use FEATURES=buildpkg instead. *** Bug 586274 has been marked as a duplicate of this bug. *** |