On Friday 17 January 2014 02:02:51 [email protected] wrote: > Maybe, a good solution is to introduce a special arch, "noarch", for such > packages (similar to what's done in the rpm world). Then, if a package is > ~noarch, it is automatically considered ~arch for all arches. Similar for > stable. The maintainer should be able to keyword ~noarch and to stabilize > noarch. Comments?
you mean * ? this already works today (at least with portage):
KEYWORDS="~*"
KEYWORDS="*"
in fact, i was planning on converting Chromium OS over to use this instead of
a list of arches. but that's because we run a simpler system of there really
only being two sets of ebuilds in the tree -- stable for all and unstable for
all.
for the ebuilds that are truly arch-specific (or otherwise need restricting),
then we'll do:
KEYWORDS="-* ~arm"
-mike
signature.asc
Description: This is a digitally signed message part.
