| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Tuesday 22 June 2004 21:49, Aron Griffis wrote: |
| 5 |
> With modifications to ekeyword I don't think that there would (almost) |
| 6 |
> any by-hand reordering necessary. It would happen automatically as |
| 7 |
> ekeyword is run on the packages by the p-maintainers and |
| 8 |
> a-maintainers. (See my response to Ciaran on the topic of ekeyword |
| 9 |
> changes) |
| 10 |
|
| 11 |
Your response doesn't really say how ekeyword would deal with already existing |
| 12 |
_some_random_arch_ as first entry. It can't. And is it worth adding all the |
| 13 |
logic to ekeyword? You can't rely on that developers are using it all the |
| 14 |
time. E.g. when I'm doing QA and want to change a keyword, I'm editing the |
| 15 |
ebuild directly, without using ekeyword. Your first idea, creating a "stable" |
| 16 |
keyword, is far simpler imho. |
| 17 |
|
| 18 |
|
| 19 |
Carsten |
| 20 |
-----BEGIN PGP SIGNATURE----- |
| 21 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 22 |
|
| 23 |
iD8DBQFA2K20VwbzmvGLSW8RAuI5AJ9D9ZrxzLWPsD/EKt+oIx2xjCAZagCghLOz |
| 24 |
6LxIfD6KkFt8zvl6XnNs0rU= |
| 25 |
=v6hU |
| 26 |
-----END PGP SIGNATURE----- |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives