From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] ARCH keywording for g-cpan?
Date: Wed, 18 May 2005 05:56:41 -0400 [thread overview]
Message-ID: <200505180556.41513.mcummings@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
This is geared mostly towards arch devs, but I'm open to any comments :)
A new version of g-cpan is about a week away. Lot of feature additions,
upgrades, code revisions (wouldn't recommend diff'ing the current to the new
because I know there's only a few lines in common). It's still 100% perl (in
fact, the old version was only 95%, so that's another improvement - no more
system calls, ick), and the big reason for even going down the road of a
rewrite was to add support for the intended split of dev-perl into new,
smaller, manageable(!) categories.
In the past, g-cpan was lumped in with portage, so it received all of the
keyword bliss of portage. When it was initially split from portage it also
inherited that keyword batch, since the version in the split and the version
in the current portage were identical. But herein lies my dilemma. While 100%
perl code means there ~shouldn't~ be any issues on any platform that can
install perl, I don't want to tick any arch's off by unmasking en masse.
Would you all prefer a bug with recommended tests for the new version? Do you
all even care? :) Let me know, on list, off list, just don't call me late at
night, it makes the wife wonder.
Mike
--
-----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 reply other threads:[~2005-05-18 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 9:56 Michael Cummings [this message]
2005-05-18 16:03 ` [gentoo-dev] ARCH keywording for g-cpan? Aron Griffis
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=200505180556.41513.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