| 1 |
On Tue, Dec 25, 2012 at 7:09 AM, Torsten Veller <tove@g.o> wrote: |
| 2 |
> Let's discuss the "specific guideline" for Perl modules. It's as follows: |
| 3 |
> |
| 4 |
> ,- http://devrel.gentoo.org/handbook/handbook.xml?part=2&chap=1#doc_chap2_sect2 |
| 5 |
> | Perl |
| 6 |
> | |
| 7 |
> | New Perl modules are to be added to portage only when one of the following |
| 8 |
> | conditions is met: |
| 9 |
> | |
| 10 |
> | a) The module(s) fulfill a dependency |
| 11 |
> | b) The module(s) cannot be handled by g-cpan |
| 12 |
> | c) The module(s) add functionality to existing ebuilds |
| 13 |
> | d) The module(s) provide tools, applications or other features (i.e. more |
| 14 |
> | than what their .PM offers) |
| 15 |
> | |
| 16 |
> | Please make sure that at least one member of the perl herders approves |
| 17 |
> | your addition. |
| 18 |
> `- |
| 19 |
> |
| 20 |
> Recently the proxy-maintainer project is repeatedly adding packages |
| 21 |
> which aren't following these guideline AFAIK. So maybe we should change |
| 22 |
> it. |
| 23 |
> |
| 24 |
> 444974 a) dev-perl/Text-Format - Various subroutines to format text 2012-12-07 |
| 25 |
> 444976 a) dev-perl/Roman - Perl module for conversion between Roman and Arabic numerals. 2012-12-03 |
| 26 |
> 446710 ?) dev-perl/FLV-AudioExtractor - Extract audio from Flash Videos 2012-12-12 |
| 27 |
> 447724 ?) dev-perl/Email-Send-Gmail - Send Messages using Gmail Mon 10:12 |
| 28 |
> |
| 29 |
> Ad a): This requirement is a little problematic: |
| 30 |
> Sometimes perl modules are needed for maintainer-wanted packages. |
| 31 |
> Sometimes the perl modules are added to the tree while the |
| 32 |
> maintainer-wanted package never are or will be. Sometimes the maintainer |
| 33 |
> are waiting for the perl team to do their work. |
| 34 |
> |
| 35 |
> Ad b): (Judging from bugreports) g-cpan doesn't seem to be really |
| 36 |
> reliable these days. I always wanted to test/verify it. But ... (random |
| 37 |
> excuse: time, motivation,...) |
| 38 |
> |
| 39 |
> I guess I don't have no problem with modifying or dropping the |
| 40 |
> requirements. The perl overlay contains hundreds of packages which |
| 41 |
> should be added to the main tree. |
| 42 |
> |
| 43 |
> The dev-perl category currently already contains the most packages |
| 44 |
> (1140 per packages.g.o). |
| 45 |
> |
| 46 |
> -- |
| 47 |
> Best regards |
| 48 |
> Torsten |
| 49 |
> |
| 50 |
|
| 51 |
I'm sure I skimmed that section of the handbook at some point for the |
| 52 |
quizzes, but I don't remember it. I think it is possible that the |
| 53 |
proxy commiter (pinkbyte) forgot about it too. |
| 54 |
|
| 55 |
I think that all of those requirements make sense. We might want to |
| 56 |
formalize a similar guideline for the python herd. |
| 57 |
|
| 58 |
Perhaps the requirements list could be copied somewhere more visible? |
| 59 |
The perl project page might get more traffic for people looking to |
| 60 |
write perl ebuilds. |
Archives