From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Minimal perl install (stage1/livecd makers might be interested?)
Date: Wed, 8 Jun 2005 10:38:58 -0400 [thread overview]
Message-ID: <200506081038.58442.mcummings@gentoo.org> (raw)
In-Reply-To: <20050607182145.GS9084@kaf.zko.hp.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Tuesday 07 June 2005 02:21 pm, Aron Griffis wrote:
> Only if the ebuild is called something other than perl, right?
> I mean, wouldn't it need to be called something like "miniperl" so
> that openssl could dep on miniperl, and perl could dep on openssl?
Actually, that's debatable, as it could just as easily be perl emerged with
the minimal flag - which is part of the mental debate I have - is it worth
it? if so, is it worth it as a separate ebuild that would need to be
maintained in parallel, or as just a use flag invoked version of the current
ebuild? The heart of the difference in the two installs lies in what core
perl modules are installed.
(fwiw, miniperl is something else entirely - it's what perl uses to bootstrap
itself)
--
-----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 --]
next prev parent reply other threads:[~2005-06-08 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 10:39 [gentoo-dev] Minimal perl install (stage1/livecd makers might be interested?) Michael Cummings
2005-06-07 18:21 ` Aron Griffis
2005-06-08 14:38 ` Michael Cummings [this message]
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=200506081038.58442.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