[gentoo-dev] Re: perl extra modules

[Michael Cummings]

Leon,

	Agreed this should be over on dev (cc'd -user just so the thread
watchers know).
	OK, so after sending that last message, I began thinking it
through, and there are at least a few packages that might have perl
module dependancies (doesn't some of the functionality of gimp require a
few perl modules to be installed? pretty sure there is at least a few
mainstream apps that have perl modules they need for some of their
plugins...).
	If it were my call (ha! ok, everyone stop laughing, I know what
that last line was worth) I'd recommend only maintaining those perl
modules that actually are depended on, and even then discouraging the
use of ebuilds for loading perl modules...er, not sure that made sense,
second whack at it...keep around those modules that are needed for other
ebuilds to succeed, but not try and replicate the cpan listings. For
starters, modules get updated sporadically - there are some modules,
still good, that haven't been touched in years because the developer was
done with it. Others get updated a lot, and that could throw a wrench if
you have apps depending on one version.

	My additional two cents (think I'm up to four now) is that perl
modules are good to have in portage when they fulfill a dependancy, but
personally I think it would be dangerous/risky to attempt to maintain an
ebuild tree for perl modules. No offense to those who have made the
ebuilds up to this point (seemant and danamark come to mind from a
recent perusal, among others), but the whole point to the -MCPAN -e
shell is that you are automatically filtering yourself into the mirror
trees and aren't relying on the main cpan server to handle your request.

	Thinking of which - for apps that depend on perl modules,
instead of building an ebuild for that module that points directly to
the module on cpan, would it be possible to instead execute a one liner
in perl that grabs and installs the module? ( perl -MCPAN -e install
PERL::MODULE)

	Ok, time for more coffee, this thinking stuff hurts.

Mike

On Mon, Jul 08, 2002 at 01:03:42PM +0100, Leon Brocard wrote:
> Michael Cummings sent the following bits through the ether:
>
> > Like I said, I'm a perl person to, and I'm not trying to rain on
> > anyone's parade, but I think adding the full cpan list is both a
> > reduplication of cpan's efforts and frankly little more than being able
> > to say "I can emerge a module instead of just using perl's built in
> > equivalent of an ebuild".
>
> I kinda agree. I've just submitted a bunch of Perl ebuilds and mostly
> it's just a case of figuring out the right dependencies and putting
> them in DEPEND. But sometimes, modules have an interactive install by
> default and so I code up a src_compile to get around that.
>
> The problem (and I've been discussing this with London Perl Mongers
> for the past week or so) is external dependencies, like XML::Parser
> needing expat or XML::LibXML needing libxml. External library
> dependencies aren't part of the Makefile.PL (this is a big problem
> really). Thus I think it makes sense to have Perl module ebuilds (or
> for a least some of the modules). I bet you most people actually use
> less than 100 modules. It may be a good idea to have some of this
> automated too.
>
> Leon
>
> ps should we move this to gentoo-dev?
> --
> Leon Brocard.............................http://www.astray.com/
> Nanoware...............................http://www.nanoware.org/
>
> ... Can you repeat the part after "Listen very carefully"?
> _______________________________________________
> gentoo-user mailing list
> gentoo-user@g.o
> http://lists.gentoo.org/mailman/listinfo/gentoo-user