On Thu, 2006-06-15 at 20:43 +0200, Jakub Moc wrote: > And again, what's this distinction good for? Well, it's useless unless > you are trying to enforce something like what you've suggested here > before, i.e. > > <quote> > I see nothing wrong with listing perl as the herd, *only* if > they have themselves as the maintainer. > </quote> > > Well of course it's wrong b/c people that don't give a damn about the > thing you've just dumped on them will get the bugs! And will need to > either remove themselves from metadata.xml or if they don't do it, will > finally end up maintaining the thing once the guy who's kindly dumped it > on them went MIA/retired.
No offense, but that's just insane. See, one of the problems that we have now is the massive amount of unmaintained crap in the tree. Half of this stuff, we don't even *realize* is unmaintained until a security bug comes along. Wouldn't it be much nicer if, for example, there were a perl app, and the maintainer went MIA and someone actually *knew* about it? I'm sorry, but the arguments you are presenting go against the idea of what herds were designed to solve, packages with a single maintainer and the maintainer disappearing. If the package is "no-herd" and only lists a maintainer, then the maintainer goes MIA, we end up with yet another unmaintained piece of junk in the tree. If it is listed as "perl" or "games" or "livecd" or whatever, then somebody (hopefully) knows about it, and can take action, such as: a) finding a maintainer, b) deciding to maintain it themselves, or c) removing it from the tree after a "last rites" email. I mean, what next, we start pissing on trees to mark our territory? A game is a game is a game. Not adding it to the games herd doesn't change what it is any more than not adding livecd-tools to the livecd herd changes it being something used for a livecd. I would much rather see something like sunrise (but not necessarily sunrise itself) used to put packages which are no longer maintained, but were once in the tree. I guess I'm just a proponent of solving the problems we already have, rather than making new ones. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
