Perl ebuild policy

Message

sermon · Post by **sermon** » Mon Sep 15, 2003 10:10 am

Greetings,

I submitted a bug containing an ebuild for the Coy package.
The bug was declared invalid because Coy is not directly used by any "application".

It is used directly by me, because I'm a developer. Following the "no ebuilds if they don't contribute directly to an application" seems clearly to discourage developers from gentoo: is this a new Linux distribution that is developer-unfriendly by design? Or are developers merely expected to each create their own ebuilds, without sharing the work --- a blatant contradiction of the very principles that got the GNU/Linux system, and others, built in the first place?

Can somebody explain to me

A) what factor I've missed that makes sense of this policy
B) who I shuold beat on to get this fixed?

Sermon

Post by **Pythonhead** » Mon Sep 15, 2003 7:29 pm

You'd probably be best off asking on the gentoo development mailing list. This policy is just for Perl modules so maybe there is a good reason for it.

I think I read that they are trying to collaborate with CPAN. Maybe they are being conservative on the Perl modules until a solution of interfacing portage with CPAN is found. Just a guess though.

You could always submit an ebuild for an app that requires your module ;)

Genone · Post by **Genone** » Mon Sep 15, 2003 7:55 pm

most ebuilds for perl modules are absolute no-brainers that contain no code at all as the perl-module eclass takes care of everything. There is some work underway to get rid of the static ebuilds and to generate them dynamically on emerge time using CPAN (g-cpan.pl can currently be used for that).
The static ebuilds have no real use and need to be maintained for new versions, so unless they are needed for dependencies they won't be added to the portage tree.

sermon · Post by **sermon** » Tue Sep 16, 2003 8:31 am

Thanks for the pointers. I'll investigate the development stuff, and see where that takes me.