1 |
On Wed, Jun 14, 2006 at 05:13:48PM -0400, Chris Gianelloni wrote: |
2 |
> On Wed, 2006-06-14 at 15:54 +0200, Harald van Dijk wrote: |
3 |
> > On Wed, Jun 14, 2006 at 09:13:34AM -0400, Chris Gianelloni wrote: |
4 |
> > > > A great example of this are web-based applications. The web-apps project |
5 |
> > > > does not own all the web-based packages in the Portage tree. There are many |
6 |
> > > > such packages in the tree that are managed by developers that are not part |
7 |
> > > > of the project. The web-apps project gets to decide what happens to the |
8 |
> > > > packages grouped in the web-apps herd, but we neither have the right (nor |
9 |
> > > > the desire) to tell other developers that they can't add web-based packages |
10 |
> > > > to the tree; nor do other developers require our permission before adding |
11 |
> > > > packages to the tree. |
12 |
> > > |
13 |
> > > Again, you are confusing herds and projects. |
14 |
> > > |
15 |
> > > Here's another example of it done correctly. If you add a game to the |
16 |
> > > tree, the herd should be listed as games. Period. Even if you are |
17 |
> > > going to be the sole maintainer of the package, games should be the |
18 |
> > > herd. Why? Because it is a game, silly. |
19 |
> > |
20 |
> > Why do no games' metadata.xml specify games@ as the maintainer? I |
21 |
> > thought it was because <herd>games</herd> implies this already, but if |
22 |
> > it doesn't, then dozens of games can be considered unmaintained right |
23 |
> > now, and fair game for anyone to mess with without approval. Are you |
24 |
> > sure you like this interpretation of 'herd'? |
25 |
> > |
26 |
> > You're probably right that herd is supposed to mean what you say it |
27 |
> > does, but existing practise, even by yourself, is very different from |
28 |
> > it. |
29 |
> |
30 |
> Umm... no. |
31 |
> |
32 |
> See, if there's no maintainer listed, it defaults to the maintaining |
33 |
> project *for that herd*... |
34 |
|
35 |
So <herd>games</herd> implies "managed by the games team" sometimes but |
36 |
not always? Meaning if the maintainer is "games team + X", then "games |
37 |
team" must be explicitly listed as a maintainer in metadata.xml ? |
38 |
|
39 |
If so, sorry, misunderstood you, and this is far less insane than what I |
40 |
thought you were saying. |
41 |
-- |
42 |
gentoo-dev@g.o mailing list |