[gentoo-perl] libperl: to keep or merge?

[gentoo-perl] libperl: to keep or merge?

[Michael Cummings]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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).



- --

- -----o()o----------------------------------------------
Michael Cummings   |    #gentoo-dev, #gentoo-perl
Gentoo Perl Dev    |    on irc.freenode.net
Gentoo/SPARC
Gentoo/AMD64
GPG: 0543 6FA3 5F82 3A76 3BF7  8323 AB5C ED4E 9E7F 4E2E
- -----o()o----------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)

iD8DBQFE2THTq1ztTp5/Ti4RAvrLAJ42ko2sEvy8EHs/9u7DYuKOnuZHpwCeJ8Ao
I2HbFAeBd8hpy7dErMnt1FA=
=ZIlM
-----END PGP SIGNATURE-----
-- 
gentoo-perl@gentoo.org mailing list

Re: [gentoo-perl] libperl: to keep or merge?

[Christian Hartmann]

> 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 always wondered about that.

> 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).

That's what the 'static' useflag is for. Let's use it. :)

+1 for merge

-- 
Christian Hartmann
http://www.gentoo.org/~ian/

PGP Key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2154E5EE692A4865
Key fingerprint = 4544 EC0C BAE4 216F 5981  7F95 2154 E5EE 692A 4865

-- 
gentoo-perl@gentoo.org mailing list

Re: [gentoo-perl] libperl: to keep or merge?

[Elfyn McBratney]

On Wed, Aug 09, 2006 at 07:32:31AM +0200, Christian Hartmann 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 always wondered about that.
 > 
 > > 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).
 > 
 > That's what the 'static' useflag is for. Let's use it. :)
 > 
 > +1 for merge

Same here, for what it's worth. :)

Best,
Elfyn

-- 
Elfyn McBratney, Gentoo Developer
+----------------------------------+
|  irc.freenode.net / beu          |
|  beu [@] gentoo [.] org          |
+-------------------------- o.0 ---+
-- 
gentoo-perl@gentoo.org mailing list

Re: [gentoo-perl] libperl: to keep or merge?

[Antoine Raillon]

Quoting Elfyn McBratney <beu@gentoo.org>:

>  > +1 for merge
> Same here, for what it's worth. :)

/me approves merging too =)


-- 
Antoine Raillon <antoine.raillon@dragou.net>
-- 
gentoo-perl@gentoo.org mailing list

Re: [gentoo-perl] libperl: to keep or merge?

[Aaron Kulbe]

[-- Attachment #1: Type: text/plain, Size: 313 bytes --]

Merge.

On 8/9/06, Antoine Raillon <antoine.raillon@dragou.net> wrote:
>
> Quoting Elfyn McBratney <beu@gentoo.org>:
>
> >  > +1 for merge
> > Same here, for what it's worth. :)
>
> /me approves merging too =)
>
>
> --
> Antoine Raillon <antoine.raillon@dragou.net>
> --
> gentoo-perl@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 770 bytes --]

Re: [gentoo-perl] libperl: to keep or merge?

[Michele Beltrame]

Hello!

> > Same here, for what it's worth. :)
> /me approves merging too =)

Merge! And "static" IUSE flag of course. ;-)

Michele.


-- 
gentoo-perl@gentoo.org mailing list

Re: [gentoo-perl] libperl: to keep or merge?

[Yuval Yaari]

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