| 1 |
Carsten Lohrke wrote: [Tue Jun 22 2004, 12:17:23PM EDT] |
| 2 |
> Not all ebuilds have a single maintainer and not all herd members |
| 3 |
> use the same architecture, so you'll have a jumping |
| 4 |
> package-maintainer-arch keyword in the end. Don't know, if that's |
| 5 |
> less complicated. |
| 6 |
|
| 7 |
I think it's okay if the maintainer's arch jumps around. To do |
| 8 |
otherwise would be an unnecessary restriction. |
| 9 |
|
| 10 |
If we go with my proposal to put the maintainer's arch first in the |
| 11 |
list, then it's just a matter of reordering the list when the |
| 12 |
maintainer marks a package stable. I can put a simple feature into |
| 13 |
ekeyword to make this easy. |
| 14 |
|
| 15 |
I'll write up a GLEP, since clearly this is an enhancement proposal. |
| 16 |
|
| 17 |
Regards, |
| 18 |
Aron |
| 19 |
|
| 20 |
-- |
| 21 |
Aron Griffis |
| 22 |
Gentoo Linux Developer |
Archives