Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-perl
Navigation:
Lists: gentoo-perl: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: <gentoo-perl@g.o>
From: "Michael Higgins" <mhiggins@...>
Subject: Big Perl Packages and g-cpan
Date: Mon, 19 Feb 2007 14:16:22 -0800
Hello, List --

Shot in the dark here... anyone on the list using any big, multi-module perl
packages but finding that g-cpan just ain't doin' it for ya?

If so, anyone find a suitable practice to avoid it? (Outside of making an
ebuild, of course.)

I've found that CPAN is just fine to use in the past. But g-cpan doesn't
seem to do much except get in the way when given a build of any real
complexity.

It seems like maybe CPAN.pm could be patched to emerge any modules
maintained the portage when needed by CPAN. If I dump g-cpan, should I also
emerge -C any modules built with portage and build them with CPAN?

Any thoughts or advice much appreciated.

Thanks,

-- 
Michael Higgins


-- 
gentoo-perl@g.o mailing list


Replies:
Re: Big Perl Packages and g-cpan
-- Michael Cummings
Navigation:
Lists: gentoo-perl: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[Patch] up2date-ng and CPAN package list
Next by thread:
Re: Big Perl Packages and g-cpan
Previous by date:
Perl ebuilds needing updates
Next by date:
Re: Big Perl Packages and g-cpan


Updated Jun 17, 2009

Summary: Archive of the gentoo-perl mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.