After raising the awareness about KEYWORDS=”-*” being a stupid thing to use in the last months today I decided to eliminate the remaining reason for using it (one couldn’t unmask a package that had KEYWORDS=”” without editing it) by adding support for a new token in package.keywords. So now when portage-2.1.3 goes live all theses live-cvs-completely-unsupported packages can stop using the broken KEYWORDS=”-*” and use KEYWORDS=”” instead without loosing functionality. And once we get the tree clean from those KEYWORDS=”-*” abusers we can also finally fix the -* handling for package.keywords to do what it should do (act like ACCEPT_KEYWORDS).
2 thoughts on “Getting rid of KEYWORDS=-*, step 2”
Comments are closed.
Or they could use package.mask with proper KEYWORDS, as was originally intended…
Of course, that’s a given. But Diego has a point in bug 160519 which is IMO a legit reason to have this option as well, in some cases dual protection makes sense. Could blame users for not using the tools (package.unmask) properly, but that’d be a bit harsh and wouldn’t really help anything.