From: Christian Hartmann <ian@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] yaml dep in g-cpan: Objections?
Date: Fri, 14 Apr 2006 17:20:01 +0200 [thread overview]
Message-ID: <200604141720.01921.ian@gentoo.org> (raw)
In-Reply-To: <20060414131314.7A91886@gnosis.datanode.net>
Am Freitag 14 April 2006 15:13 schrieb Michael Cummings:
> I'm thinking of forcing a dep on dev-perl/yaml in the next release of
> g-cpan. (Assuming all goes well) I've been working on the dep check code
> this morning, and it appears to be working great, but a portion of it
> relies on yaml (in the presence of a META.yml file of course). Anyone
> think of any objections to this?
Nope. Sounds reasonable to me.
--
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
prev parent reply other threads:[~2006-04-14 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 13:13 [gentoo-perl] yaml dep in g-cpan: Objections? Michael Cummings
2006-04-14 15:20 ` Christian Hartmann [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=200604141720.01921.ian@gentoo.org \
--to=ian@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