| 1 |
Extracted from what Henrik Brix Andersen wrote: |
| 2 |
> That's not a valid argument - you can use a bash function for calling |
| 3 |
> echangelog and repoman as shown numerous times on this list. |
| 4 |
|
| 5 |
|
| 6 |
> See my first answer (bash function). |
| 7 |
|
| 8 |
|
| 9 |
> See my first answer (bash function). |
| 10 |
|
| 11 |
|
| 12 |
From a database point of view, it is evil to duplicate values in an |
| 13 |
automated manner, just use a foreign key for such purposes. In other |
| 14 |
words, avoid duplication. If such bash function is a common tool then |
| 15 |
-- apart from wondering why it isn't part of the default suite -- this |
| 16 |
anti-duplication constraint is being broken massively. I like Mike's |
| 17 |
idea, because it deals with data redundancy and basically uses this |
| 18 |
'foreign key' for the changelog. |
| 19 |
|
| 20 |
In other words: centralise the administration, don't make yourself |
| 21 |
having to keep multiple copies up-to-date, you're doomed to make errors |
| 22 |
with that. |
| 23 |
|
| 24 |
Just my two cents. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Fabian Groffen |
| 29 |
eBuild && Porting |
| 30 |
Gentoo for Mac OS X |
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives