public inbox for gentoo-perl@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yuval Yaari <yyuval@checkpoint.com>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] libperl: to keep or merge?
Date: Wed, 09 Aug 2006 12:58:43 +0300	[thread overview]
Message-ID: <44D9B1D3.9040404@checkpoint.com> (raw)
In-Reply-To: <44D931D3.9050605@gentoo.org>

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@gentoo.org mailing list



      parent reply	other threads:[~2006-08-09  9:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09  0:52 [gentoo-perl] libperl: to keep or merge? Michael Cummings
2006-08-09  5:32 ` Christian Hartmann
2006-08-09  6:41   ` Elfyn McBratney
2006-08-09  7:14     ` Antoine Raillon
2006-08-09  8:52       ` Aaron Kulbe
2006-08-09 23:41       ` Michele Beltrame
2006-08-09  9:58 ` Yuval Yaari [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44D9B1D3.9040404@checkpoint.com \
    --to=yyuval@checkpoint.com \
    --cc=gentoo-perl@gentoo.org \
    --cc=gentoo-perl@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox