Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-perl
Navigation:
Lists: gentoo-perl: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-perl@g.o
From: Michael Cummings <mcummings@g.o>
Subject: Re: g-cpan -u
Date: Mon, 14 Nov 2005 17:18:08 -0500
Chisel Wright wrote:
> On Mon, Nov 14, 2005 at 09:09:15PM +0000, Chisel Wright wrote:
> 
> I've only skimmed over g-cpan.pl, but I can't see anywhere in sub
> upgrade_module{} where the CPAN version is compared against the
> currently installed version.
> 

I could try the old developer trick of "in the next version..." - but 
the short of it is, you're right, we cheat here. Instead of expending 
time on checking module versions (which seem to change numbering schemes 
between releases sometimes), we just check to see if we need to make an 
ebuild for it or if one already exists (after making sure we are in 
$OVERLAY/perl-gcpan of course, and not upgrading your 'real' tree) - 
then we just rely on portage to handle the -u for anything that has an 
ebuild greater than what's installed. Cheap, tawdry - sure beat writing 
version checkers (or adding deps for one)(or stealing more code from how 
cpan handles it, which I will show off in the next version with some new 
fangled dep checking).

-- 
gentoo-perl@g.o mailing list


Replies:
Re: g-cpan -u
-- Yuval Yaari
References:
g-cpan -u
-- Chisel Wright
Re: g-cpan -u
-- Chisel Wright
Re: g-cpan -u
-- Michael Cummings
Re: g-cpan -u
-- Chisel Wright
Re: g-cpan -u
-- Chisel Wright
Navigation:
Lists: gentoo-perl: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: g-cpan -u
Next by thread:
Re: g-cpan -u
Previous by date:
Collision Protects
Next by date:
Re: Collision Protects


Updated Jun 17, 2009

Summary: Archive of the gentoo-perl mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.