public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Minimal perl install (stage1/livecd makers might be interested?)
Date: Tue, 7 Jun 2005 06:39:28 -0400	[thread overview]
Message-ID: <200506070639.28941.mcummings@gentoo.org> (raw)

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

I have me a bug, but before I finish weighing in with my own pros and cons, I 
thought I'd ask -dev, in particular since I know the creators of things like 
catalyst and such are on here, and the results of this particular bug 
(feature request) might be of interest to them.

A brave (perhaps bored, perhaps just frustrated) user has come up with an 
ebuild ( http://bugs.gentoo.org/show_bug.cgi?id=95038 ) that should (he says 
it does, but I haven't had a chance to set up a chroot to test it in) build 
an extremely minimal perl that's capable of some core perl functionality and 
litte else out of the box. Now for the perl herd, this would imply that we 
would need to come up with some more perl-core/* ebuilds to fill in any gaps 
that the minimal perl install has.

Cons are the addition of a bunch of ebuilds to cover the functionality that 
the minimal install lacks.

Pros, though, are pretty big, once getting past the first hurtle of pain. We 
would be able to eliminate the conflicts between perl coming with module foo 
and ebuild for foo, which is usually at or greater than the same version as 
the one that came with perl (usually greater) A lot of our collision protect 
bugs would dissipate rapidly I think. It would save space (with his use 
flags/architecture, perl went from 12,300K to 930K) on livecd's. I have a 
weak unfounded suspicion that it might help with the whole openssl->perl loop 
that expresses itself when some folks are building a stage1.

I'm completely on the fence here, so any feedback welcome :)

-- 

-----o()o---------------------------------------------
Michael Cummings   |    #gentoo-dev, #gentoo-perl
Gentoo Perl Dev    |    on irc.freenode.net 
-----o()o---------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-06-07 10:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 10:39 Michael Cummings [this message]
2005-06-07 18:21 ` [gentoo-dev] Minimal perl install (stage1/livecd makers might be interested?) Aron Griffis
2005-06-08 14:38   ` Michael Cummings
2005-06-07 19:04 ` Robin H. Johnson
2005-06-07 19:45   ` Aron Griffis
2005-06-08  7:21     ` Robin H. Johnson
2005-06-08 14:41       ` Michael Cummings
2005-06-08 15:05         ` Chris Gianelloni
2005-06-08 15:24           ` Michael Cummings
2005-06-07 22:22 ` Chris Gianelloni
2005-06-08 14:36   ` Michael Cummings

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=200506070639.28941.mcummings@gentoo.org \
    --to=mcummings@gentoo.org \
    --cc=gentoo-dev@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