From: Daniel Westermann-Clark <daniel@acceleration.net>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Adding perl-core/Encode?
Date: Tue, 10 Jan 2006 10:36:44 -0500 [thread overview]
Message-ID: <20060110153644.GC12693@dulcinea.dwc.homedns.org> (raw)
In-Reply-To: <43C3ED48.8020003@checkpoint.com>
On 2006-01-10 17:22:16 +0000, Yuval Yaari wrote:
> Before you start unmasking, lest we forget that dev-util/svk is
> masked by itself, anyway.
Yeah, I'm fine with unmasking perl-5.8.7 locally where I need SVK.
It's not a problem, I was more curious about perl-core policy than
anything else.
> Daniel, what's the big difference between Encode 2.08 and 2.10
> (provided by perl 5.8.6 and 5.8.7 respectively, IIRC)?
Mostly UTF-8 fixes, according to the Changes file. I don't know
specifically why SVK claims it needs 2.10.
--
Daniel Westermann-Clark
--
gentoo-perl@gentoo.org mailing list
prev parent reply other threads:[~2006-01-10 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 15:10 [gentoo-perl] Adding perl-core/Encode? Daniel Westermann-Clark
2006-01-10 15:14 ` Michael Cummings
2006-01-10 15:30 ` Daniel Westermann-Clark
2006-01-10 17:22 ` Yuval Yaari
2006-01-10 15:36 ` Daniel Westermann-Clark [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=20060110153644.GC12693@dulcinea.dwc.homedns.org \
--to=daniel@acceleration.net \
--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