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