| 1 |
On Friday 17 January 2014 02:02:51 grozin@g.o wrote: |
| 2 |
> Maybe, a good solution is to introduce a special arch, "noarch", for such |
| 3 |
> packages (similar to what's done in the rpm world). Then, if a package is |
| 4 |
> ~noarch, it is automatically considered ~arch for all arches. Similar for |
| 5 |
> stable. The maintainer should be able to keyword ~noarch and to stabilize |
| 6 |
> noarch. Comments? |
| 7 |
|
| 8 |
you mean * ? this already works today (at least with portage): |
| 9 |
KEYWORDS="~*" |
| 10 |
KEYWORDS="*" |
| 11 |
|
| 12 |
in fact, i was planning on converting Chromium OS over to use this instead of |
| 13 |
a list of arches. but that's because we run a simpler system of there really |
| 14 |
only being two sets of ebuilds in the tree -- stable for all and unstable for |
| 15 |
all. |
| 16 |
|
| 17 |
for the ebuilds that are truly arch-specific (or otherwise need restricting), |
| 18 |
then we'll do: |
| 19 |
KEYWORDS="-* ~arm" |
| 20 |
-mike |
Archives