public inbox for gentoo-perl@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Cc: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Another g-cpan question
Date: Mon, 17 Apr 2006 17:13:33 -0400	[thread overview]
Message-ID: <1145308413.25288.1.camel@tardis.datanode.net> (raw)
In-Reply-To: <1145303672.4132.6.camel@tardis.datanode.net>

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

As is often enough the case, soon as I sent this off I realized that
there was really only one 'economical' solution. Sorry for the traffic
folks.

~mcummings

On Mon, 2006-04-17 at 15:54 -0400, Michael Cummings wrote:
> That's right folks, shape the future of the next release of g-cpan!
> 
> *cough* *cough*
> 
> OK, next question I'm torn on (btw, verdict with 2 whole feedbacks was
> that YAML was an acceptable dep). I'm in a position where I can tweak
> some simple code based on the more comprehensive dep list and list DEPs,
> or I can take some time (and time == slightly larger memory footprint)
> and maintain module-version in the DEP list. Thoughts? On the one hand,
> g-cpan is a "for entertainment purposes only" tool, ie, the ebuilds it
> generates are intended for use on your box only, not for mass
> distribution to the masses (for starters, there's no such thing as QA on
> what its doing - its the risk you take using something that blindly
> installs cpan modules). On the other hand, the power is there to do
> it...opinions?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-perl@gentoo.org
Cc: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Another g-cpan question
Date: Mon, 17 Apr 2006 17:13:33 -0400	[thread overview]
Message-ID: <1145308413.25288.1.camel@tardis.datanode.net> (raw)
Message-ID: <20060417211333.xn9p5S0bzRZ7brnhq0I1xGDVnpedWUS2wwtuksWI3aU@z> (raw)
In-Reply-To: <1145303672.4132.6.camel@tardis.datanode.net>

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

As is often enough the case, soon as I sent this off I realized that
there was really only one 'economical' solution. Sorry for the traffic
folks.

~mcummings

On Mon, 2006-04-17 at 15:54 -0400, Michael Cummings wrote:
> That's right folks, shape the future of the next release of g-cpan!
> 
> *cough* *cough*
> 
> OK, next question I'm torn on (btw, verdict with 2 whole feedbacks was
> that YAML was an acceptable dep). I'm in a position where I can tweak
> some simple code based on the more comprehensive dep list and list DEPs,
> or I can take some time (and time == slightly larger memory footprint)
> and maintain module-version in the DEP list. Thoughts? On the one hand,
> g-cpan is a "for entertainment purposes only" tool, ie, the ebuilds it
> generates are intended for use on your box only, not for mass
> distribution to the masses (for starters, there's no such thing as QA on
> what its doing - its the risk you take using something that blindly
> installs cpan modules). On the other hand, the power is there to do
> it...opinions?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-04-17 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 19:54 [gentoo-perl] Another g-cpan question Michael Cummings
2006-04-17 21:13 ` Michael Cummings [this message]
2006-04-17 21:13   ` 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=1145308413.25288.1.camel@tardis.datanode.net \
    --to=mcummings@gentoo.org \
    --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