On Mon, Jun 27, 2011 at 22:46, Petteri Räty <betelge...@gentoo.org> 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
