| 1 |
Carsten Lohrke wrote: [Tue Jun 22 2004, 02:31:11PM EDT] |
| 2 |
> I'm not editing ebuilds via repoman. ;) |
| 3 |
|
| 4 |
But you had better hope you're committing them that way. ;-) |
| 5 |
|
| 6 |
> And it is not as non-invasive as you think. Quite a fey keyword |
| 7 |
> lines would need to be reordered to adhere the new rule - by hand. |
| 8 |
> It is far easier to use +arch and let portage and all tools |
| 9 |
> interpret it as arch (as it is now, maybe printing a warning), until |
| 10 |
> portage, all tools and ebuilds are ready to switch to the new |
| 11 |
> explicit stable feature. |
| 12 |
|
| 13 |
With modifications to ekeyword I don't think that there would (almost) |
| 14 |
any by-hand reordering necessary. It would happen automatically as |
| 15 |
ekeyword is run on the packages by the p-maintainers and |
| 16 |
a-maintainers. (See my response to Ciaran on the topic of ekeyword |
| 17 |
changes) |
| 18 |
|
| 19 |
On the other hand, I'm not opposed completely to a specially marked |
| 20 |
keyword. But there are some things we need to realize: (1) each |
| 21 |
approach will have its pros and cons, (2) whichever approach we choose |
| 22 |
will likely compromise in one area to avoid compromising in another |
| 23 |
area... |
| 24 |
|
| 25 |
Regards, |
| 26 |
Aron |
| 27 |
|
| 28 |
-- |
| 29 |
Aron Griffis |
| 30 |
Gentoo Linux Developer |
Archives