| 1 |
On Thu, 15 Jun 2006 11:57:21 +0200 |
| 2 |
Jakub Moc <jakub@g.o> wrote: |
| 3 |
|
| 4 |
> Mike Frysinger wrote: |
| 5 |
> > On Thursday 15 June 2006 02:33, Kevin F. Quinn wrote: |
| 6 |
> >> We could require that a herd mail alias be maintained for every |
| 7 |
> >> herd, with the same name as the herd, such that the herd alias |
| 8 |
> >> lists the maintainers of all packages in the herd. |
| 9 |
> > |
| 10 |
> > this would be useful regardless |
| 11 |
> > -mike |
| 12 |
> |
| 13 |
> Two notes here: |
| 14 |
> |
| 15 |
> - same name as herd requirement doesn't work for stuff like |
| 16 |
> cron/mysql/postgresql/apache... i.e., system accounts. |
| 17 |
|
| 18 |
Herd aliases could be named "herd-<name>", perhaps. |
| 19 |
|
| 20 |
> - needs to be done tree-wide (for packages that have metadata.xml at |
| 21 |
> least :P - ebuilds w/o metadata is topic for another thread). Until |
| 22 |
> it's completed, it's not useful - you still cannot rely upon the |
| 23 |
> assumption that if herd alias ain't in <maintainer>, they don't |
| 24 |
> maintain the thing. |
| 25 |
> |
| 26 |
> Otherwise yeah, +1 - and it's already done this way in many ebuilds, |
| 27 |
> i.e., the herd alias is in <maintainer> as well. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Kevin F. Quinn |
Archives