| 1 |
On Friday 10 June 2005 10:55 am, foser wrote: |
| 2 |
> > If everyone starts using ekeyword now with the alphabetical ordering |
| 3 |
> > built in, everything will be consistent, and there shouldn't be a |
| 4 |
> > problem. |
| 5 |
> |
| 6 |
> even vapier indicates |
| 7 |
> that there really is no reason to do it alphabetically, except maybe |
| 8 |
> that he now knows to look in the keywords string, which is of course a |
| 9 |
> bit far fetched with all arch keywords not being set for all different |
| 10 |
> packs (so he still has to look at different points in different packs) |
| 11 |
> and was not brought up as a defence of his particular move at the time |
| 12 |
> he started doing this. |
| 13 |
|
| 14 |
not quite sure where you're pulling this out of but you're always full of |
| 15 |
suprises like this |
| 16 |
|
| 17 |
consistency is one advantage (which i'm sure you'll say is pointless) |
| 18 |
|
| 19 |
as for the rest of the ramble you posted here it's really quite wrong ... you |
| 20 |
must have missed the class where they teach you the ins & outs of |
| 21 |
alphabetical sorting because it really does allow you to quickly scan a list |
| 22 |
and figure out if the item you're looking for is there or not |
| 23 |
|
| 24 |
if you ever had to do arch-specific KEYWORDing on a frequent basis (and i'm |
| 25 |
99% sure you have nfc we support other arches than x86 if we use |
| 26 |
arch-specific breakage in GNOME depends as any sort of track record), you'd |
| 27 |
know that scattered KEYWORDS is a pita to deal with ... i've seen cases where |
| 28 |
a specific arch was duplicated in KEYWORDS; once near the beginning and once |
| 29 |
near the end ... normally it wasnt anything bad, but there was a case where |
| 30 |
one KEYWORD was stable while the other was unstable |
| 31 |
-mike |
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives