1 |
25.12.2012 18:30, Mike Gilbert wrote: |
2 |
> On Tue, Dec 25, 2012 at 7:09 AM, Torsten Veller <tove@g.o> wrote: |
3 |
>> Let's discuss the "specific guideline" for Perl modules. It's as follows: |
4 |
>> |
5 |
>> ,- http://devrel.gentoo.org/handbook/handbook.xml?part=2&chap=1#doc_chap2_sect2 |
6 |
>> | Perl |
7 |
>> | |
8 |
>> | New Perl modules are to be added to portage only when one of the following |
9 |
>> | conditions is met: |
10 |
>> | |
11 |
>> | a) The module(s) fulfill a dependency |
12 |
>> | b) The module(s) cannot be handled by g-cpan |
13 |
>> | c) The module(s) add functionality to existing ebuilds |
14 |
>> | d) The module(s) provide tools, applications or other features (i.e. more |
15 |
>> | than what their .PM offers) |
16 |
>> | |
17 |
>> | Please make sure that at least one member of the perl herders approves |
18 |
>> | your addition. |
19 |
>> `- |
20 |
>> |
21 |
>> Recently the proxy-maintainer project is repeatedly adding packages |
22 |
>> which aren't following these guideline AFAIK. So maybe we should change |
23 |
>> it. |
24 |
>> |
25 |
>> 444974 a) dev-perl/Text-Format - Various subroutines to format text 2012-12-07 |
26 |
>> 444976 a) dev-perl/Roman - Perl module for conversion between Roman and Arabic numerals. 2012-12-03 |
27 |
>> 446710 ?) dev-perl/FLV-AudioExtractor - Extract audio from Flash Videos 2012-12-12 |
28 |
>> 447724 ?) dev-perl/Email-Send-Gmail - Send Messages using Gmail Mon 10:12 |
29 |
>> |
30 |
>> Ad a): This requirement is a little problematic: |
31 |
>> Sometimes perl modules are needed for maintainer-wanted packages. |
32 |
>> Sometimes the perl modules are added to the tree while the |
33 |
>> maintainer-wanted package never are or will be. Sometimes the maintainer |
34 |
>> are waiting for the perl team to do their work. |
35 |
>> |
36 |
>> Ad b): (Judging from bugreports) g-cpan doesn't seem to be really |
37 |
>> reliable these days. I always wanted to test/verify it. But ... (random |
38 |
>> excuse: time, motivation,...) |
39 |
>> |
40 |
>> I guess I don't have no problem with modifying or dropping the |
41 |
>> requirements. The perl overlay contains hundreds of packages which |
42 |
>> should be added to the main tree. |
43 |
>> |
44 |
>> The dev-perl category currently already contains the most packages |
45 |
>> (1140 per packages.g.o). |
46 |
>> |
47 |
>> -- |
48 |
>> Best regards |
49 |
>> Torsten |
50 |
>> |
51 |
> |
52 |
> I'm sure I skimmed that section of the handbook at some point for the |
53 |
> quizzes, but I don't remember it. I think it is possible that the |
54 |
> proxy commiter (pinkbyte) forgot about it too. |
55 |
|
56 |
No, i do not, i have read this guideline, and yes - it is not mentioned |
57 |
directly in Handbook or Devmanual. |
58 |
Some of these modules was added cause they are dependencies for other |
59 |
packages(which are still waiting for adding in tree, cause they have no |
60 |
maintainer yet), others - cause g-cpan generate very ugly ebuilds for them. |
61 |
|
62 |
> I think that all of those requirements make sense. We might want to |
63 |
> formalize a similar guideline for the python herd. |
64 |
> |
65 |
> Perhaps the requirements list could be copied somewhere more visible? |
66 |
> The perl project page might get more traffic for people looking to |
67 |
> write perl ebuilds. |
68 |
> |
69 |
|
70 |
Truly, i do not really understand such hard policy for NOT including |
71 |
perl modules in tree. I know that perl herd is understaffed, but i do |
72 |
not think that this is generally a problem, cause they do not maintain |
73 |
recently added packages, but proxy maintainers do. |
74 |
|
75 |
So, basically, yes, i vote for easing policy a bit. |
76 |
|
77 |
P.S. CCing maintainer of modules, that i have commited as a proxy, maybe |
78 |
he also wants to say something regarding this. |
79 |
|
80 |
-- |
81 |
Best regards, Sergey Popov |
82 |
Gentoo Linux Developer |
83 |
Desktop-effects project lead |