From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] [RFC] Some thoughts on the next release of perl
Date: Tue, 3 Apr 2007 12:22:02 -0400 [thread overview]
Message-ID: <20070403162202.GB20273@paradox.datanode.net> (raw)
In-Reply-To: <20070403154217.GB7047@home.power>
[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]
On Tue, Apr 03, 2007 at 06:42:17PM +0300, Alex Efros wrote:
> Hi!
>
> On Tue, Apr 03, 2007 at 07:40:19AM -0400, Michael Cummings wrote:
> > * Redoing the re-order @INC patch - I've had discussions lately with folks, both
>
> Good idea. Right now I use workaround to use my modules in site_perl:
> 1) I've installed fresh modules from CPAN.
> 2) I've unmerged Gentoo's modules (because of @INC re-ordering issue).
> 3) I've fill /etc/portage/profile/package.provided to avoid installing them
> again by emerge -uDNa world. I use something like:
>
> { perl -le 'use DBI; print "dev-perl/DBI-", $DBI::VERSION';
> perl -le 'use DBD::mysql; print "dev-perl/DBD-mysql-", $DBD::mysql::VERSION';
> perl -le 'use XML::Simple;print "dev-perl/XML-Simple-",$XML::Simple::VERSION';
> perl -le 'use XML::Parser;print "dev-perl/XML-Parser-",$XML::Parser::VERSION';
> } >> /etc/portage/profile/package.provided
>
> Maybe it's good idea to automate this in some way...
rather than use $MODULE::VERSION, you may want to use a hard number (like 9999)
- I only mention it because sometimes we have to alter the upstream version
numbers so that portage can understand that version 0.5 is greater than version
0.401 (which portage doesn't interpret as a decimal, but instead as a version
seperator). Just something to think about :) (though I think getting the reorder
patch updated would help you out a lot too).
~mcummings
--
-----o()o----------------------------------------------
Michael Cummings | #gentoo-dev, #gentoo-perl
Gentoo Perl Dev | on irc.freenode.net
Gentoo/SPARC
Gentoo/AMD64
GPG: 0543 6FA3 5F82 3A76 3BF7 8323 AB5C ED4E 9E7F 4E2E
-----o()o----------------------------------------------
Hi, I'm a .signature virus! Please copy me in your ~/.signature.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-03 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 11:40 [gentoo-perl] [RFC] Some thoughts on the next release of perl Michael Cummings
2007-04-03 15:42 ` Alex Efros
2007-04-03 16:22 ` Michael Cummings [this message]
2007-04-04 8:11 ` Christian Hartmann
2007-04-04 21:46 ` Michael Cummings
2007-04-04 21:58 ` Jeff Rollin
2007-04-04 14:08 ` Antoine Raillon
2007-04-04 21:50 ` 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=20070403162202.GB20273@paradox.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