| 1 |
On Wed, 01 Oct 2003 00:53:18 -0600 |
| 2 |
Daniel Robbins <drobbins@g.o> wrote: |
| 3 |
|
| 4 |
> 5. Respect herds and existing maintainers. Look at the Changelog and |
| 5 |
> metadata.xml. If the last committer is not an active dev, it is |
| 6 |
> certainly OK to take some initiative and close the bug yourself. But |
| 7 |
> see if they're active first. If they are, you might want to get their |
| 8 |
> input first (depending on the complexity of the package.) Beware of |
| 9 |
> important libraries and system packages, which should be treated with |
| 10 |
> the utmost care and deferred to the official maintainer(s) (according |
| 11 |
> to metadata.xml or ChangeLog.) |
| 12 |
|
| 13 |
I'll take this opportunity to promote the script I'm currently |
| 14 |
developing. One of its purposes is to find packages that don't have a |
| 15 |
metadata.xml file. Another goody of its functions is the possibility to |
| 16 |
search for the maintainer of a certain package. |
| 17 |
For example, if you specify a package without a metadata.xml file, it |
| 18 |
will parse the ChangeLog and return the developer with most ChangeLog |
| 19 |
entries. On the other hand, if the package you specified has a |
| 20 |
metadata.xml file, it will parse the information given in there. |
| 21 |
|
| 22 |
It still needs some improvement and I'm currently in the middle of |
| 23 |
rewriting it (possibly integrate the use portage.py's functions instead |
| 24 |
of my own; but this will require some speed benchmarking...). |
| 25 |
I'm open for suggestions and improvements you might come up with. |
| 26 |
|
| 27 |
If you're interested you can check the current stable and pre releases |
| 28 |
over here: |
| 29 |
http://dev.gentoo.org/~pyrania/metadata/ |
| 30 |
|
| 31 |
-- Markus |
| 32 |
|
| 33 |
-- |
| 34 |
Markus Nigbur |
| 35 |
Gentoo Developer |
| 36 |
http://www.gentoo.org |
Archives