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: Yuval Yaari <yyuval@...>
Subject: Re: libperl: to keep or merge?
Date: Wed, 09 Aug 2006 12:58:43 +0300
Michael Cummings wrote:
> OK, I think I floated this idea a while back, but it was while I was
> trying that zany slotted perl ebuild stuff, and it never made it any
> further. Right now we have an ebuild for libperl to build a the shared
> library, and the in the regular perl ebuild we build a huge honking
> static perl.
>
> I can see some of the rationale of this historically - on a fried box, a
> static perl will still run, whereas a dynamic one will be dead if
> /usr/lib is toasted.
>
> But seriously, do we really need to keep these separate? Wouldn't a
> (pseudo-ebuild syntax) IUSE="...static" and a if static? (myconf=$myconf
> - -Dstatic_option) else ( myconf=$myconf -Ddynamic_option) work? (yeah,
> that was really bad pseudo-ebuild code, you get the drift).
>   
$merge++;

Would make SLOTted Perl easier ;-)

  ~Y
-- 
gentoo-perl@g.o mailing list


References:
libperl: to keep or merge?
-- Michael Cummings
Navigation:
Lists: gentoo-perl: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: libperl: to keep or merge?
Next by thread:
Proposed perl-module.eclass additions
Previous by date:
Re: libperl: to keep or merge?
Next by date:
Re: Perl ebuilds needing updates


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.