-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone,
At least a few people have expressed a desire to have support for a package.keywords file in the profiles [1] as a means to add or subtract any number values to or from the KEYWORDS that apply to a given ebuild. This would allow a specific profile to alter which packages are visible to consumers of a given keyword. This is useful for profiles that differ from other profiles in some significant way despite sharing the same values for stable and unstable keywords. For example, embedded profiles which use uclibc instead of glibc. An alternative solution for some cases might be to introduce additional keywords values, such as those suggested in GLEP 22 [2]. However, the package.keywords approach may provide greater simplicity and flexibility which would allow it to serve as a solution for a larger number of use cases. For example, the uclibc profiles would not have to maintain separate keywords for every single package. Since older versions of portage will simply ignore package.keywords files that may exist in a given profile, care should be taken not to use package.keywords in older profiles that are known to be used by older versions of portage. Does package.keywords seem like a good solution for the types of problems it's meant to solve? Would anybody like to discuss any alternative approaches? [1] http://bugs.gentoo.org/show_bug.cgi?id=55321 [2] http://www.gentoo.org/proj/en/glep/glep-0022.html - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiowSgACgkQ/ejvha5XGaPb7wCcCldP1W7KBC+h5Klbvo9ccAc8 NiMAn3pnk17jbEKQ5AZnJjKHNTTE4OP9 =0jTA -----END PGP SIGNATURE-----
