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: Petteri Räty <betelgeuse@g.o>
Subject: Re: The Python problem
Date: Mon, 27 Jun 2011 23:46:11 +0300
On 27.06.2011 19:00, Dirkjan Ochtman wrote:
> On Mon, Jun 27, 2011 at 17:53, Petteri Räty <betelgeuse@g.o> wrote:
>> I like the ruby approach for the reason that it doesn't require users to
>> run update scripts like python-updater.
> 
> 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.

Regards,
Petteri

Attachment:
signature.asc (OpenPGP digital signature)
Replies:
Re: The Python problem
-- Dirkjan Ochtman
References:
The Python problem
-- Dirkjan Ochtman
Re: The Python problem
-- Petteri Räty
Re: The Python problem
-- Dirkjan Ochtman
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: The Python problem
Next by thread:
Re: The Python problem
Previous by date:
Re: Don't use / when applying sed with CFLAGS
Next by date:
Re: The Python problem


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.