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-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Dirkjan Ochtman <djc@g.o>
Subject: Re: The Python problem
Date: Tue, 28 Jun 2011 10:06:53 +0200
On Mon, Jun 27, 2011 at 22:46, Petteri Räty <betelgeuse@g.o> wrote:
>> Sure, but if that means the developers now have to bump every package
>> in the tree when a new version of Python comes out, I'm not sure
>> that's the best trade-off.
>
> And why can't this be handled by the eclass? If the ebuild is able to
> specify it supports >=3.0 meaning it's expected that future versions
> work then the eclass can make the new values available through IUSE when
> new python versions are out and ebuilds don't require any changes.

I'd be happy to get that to work, it seems like a good solution.

Cheers,

Dirkjan


Replies:
REMOVE
-- Stelios Boulios
References:
The Python problem
-- Dirkjan Ochtman
Re: The Python problem
-- Petteri Räty
Re: The Python problem
-- Dirkjan Ochtman
Re: The Python problem
-- Petteri Räty
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: The Python problem
Next by thread:
REMOVE
Previous by date:
Re: The Python problem
Next by date:
REMOVE


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

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