| 1 |
> Submit an updated ebuild. |
| 2 |
|
| 3 |
why should I update an ebuild I have nothing to do with ? |
| 4 |
Then we would have the result gentoo is currently experiencing with many |
| 5 |
packages IMHO. |
| 6 |
I don't use osp, but the ebuild is useless for people who do use osp...If |
| 7 |
there would be a maintainer he could update it or people (like me) report |
| 8 |
that there is a new version, but if the dev who is in mood for osp updates it |
| 9 |
sometime nobody feels responsible (like it seems it's the case with some |
| 10 |
not-so-popular packages). |
| 11 |
Also if a developer leaves the team (and that happens from time to time ;) the |
| 12 |
ebuild is just dead if no new maintainer is assigned to the ebuild (also |
| 13 |
seems to happen to a few packages) |
| 14 |
|
| 15 |
> Read changelogs. |
| 16 |
|
| 17 |
You won't believe it but in fact, I really do so. |
| 18 |
But what's the point about making a changelog entry which tells me "version |
| 19 |
bump" though a diff shows some more changes and should I assume that the one |
| 20 |
who subbmitted the most recent ebuild is also the maintainer ? |
| 21 |
|
| 22 |
> We have real maintainers. For example, I maintain a handful of packages. |
| 23 |
> |
| 24 |
> Could you be more specific about what constitutes a "real" maintainer? |
| 25 |
|
| 26 |
that means e.g. having something like MAINTAINER="xxxx@g.o" in the |
| 27 |
ebuild. |
| 28 |
I believe that you are maintaining packages, many people do so, too. But the |
| 29 |
maintainers should be "hardcoded" in some way just like debian does (they |
| 30 |
have also about 9.000 packages...they have some non-maintained packages, too |
| 31 |
but then you _know_ that the maintainer isn't working on it anymore or |
| 32 |
something like that in gentoo you don't know that...Additionally I hear |
| 33 |
complains that some bugs get assigned to people on bugs.gentoo.org that have |
| 34 |
nothing to do with the bug/package, just because they submitted a new ebuild |
| 35 |
for a package to fix something and then they are meant to be the maintainer ? |
| 36 |
|
| 37 |
There are packages where you can't see what developer carrys about them...you |
| 38 |
often have the choice between two or more (or sometimes none since all people |
| 39 |
mentioned in the changelog aren't in the dev team anymore ;) |
| 40 |
|
| 41 |
Again, I don't know how it's working internally but from a users perspective |
| 42 |
gentoo's maintaining system is quite poor (if you take the packages in the |
| 43 |
tree...recently we broke the 40k files to consider barrier...if you have that |
| 44 |
many files (sure, changelogs, patches etc. are included but anyway ;) a |
| 45 |
"I-care-about-what-I-like" doesn't work for not-so-popular packages... |
| 46 |
I don't say this is the case for most packages...It just happens to quite a |
| 47 |
few and not only two or three. |
| 48 |
|
| 49 |
Rainer |
| 50 |
|
| 51 |
-- |
| 52 |
gentoo-dev@g.o mailing list |
Archives