Summary: | feature-request: adding masked packages automatically to /etc/portage/package.* | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Tristan Cebulla <equinox> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic-p-2799133.html#2799133 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | "supermerge" script |
Description
Tristan Cebulla
2005-10-17 03:47:11 UTC
Created attachment 70839 [details]
"supermerge" script
Masked status is different from unstable keywording. What you're suggesting is effectively castrating masked status so it means nothing, which isn't going to occur Consider if I had realplayer package.keyworded; a unstable version is package.masked due to security issues. Automatically unmasking it would expose me to that version with holes in it, despite the fact it's masked, and the only thing I told portage to do was let me use ~arch versions of the pkg. |