On Sunday 19 January 2014 04:28:33 Pacho Ramos wrote: > El dom, 19-01-2014 a las 03:36 -0500, Mike Frysinger escribió: > > 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" > > I had no idea that existed :O, I guess something related with > "specification" is missing? :/
specs are for chumps! although PMS documents -* already, so * and ~* is a logical extension. i suspect on the portage side the history is related to package.keywords support. but i'm just guessing. -mike
signature.asc
Description: This is a digitally signed message part.
