Subject: Re: time to change PYTHON_VERSION_DEFAULT to 24?
To: Greg Troxel <email@example.com>
From: David Brownlee <abs@NetBSD.org>
Date: 07/24/2006 10:23:32
I've bee running with 2.4 for a while, of course I only really
use trac and subversion...
On Mon, 24 Jul 2006, Greg Troxel wrote:
> Peter Schuller <firstname.lastname@example.org> writes:
>>>> I wanted to package cvs20hg in wip, but ran into the problem that
>>>> rcsparse (a dependency of cvs20hg) requires Python 2.4. cvs20hg requires
>>>> both rcsparse and the mercurial libraries; so if devel/mercurial has been
>>>> installed with Python 2.3, there is breakage.
>>> How about taking the easy way out of making mercurial only accept python24?
>> That certainly solves my particular problem.
>> I guess the only real situation where that might not be appropriate is if
>> there are mercurial extensions that don't work with 2.4 for some reason.
> It's starting to seem awkward for python's default to be at 2.3, when
> there are increasinly many packages that need 2.4. I tried to build
> some things that depended on a 2.4-only package and gave up, adding
> PYTHON_VERSION_DEFAULT= 24
> to /etc/mk.conf, which resulted in successful builds.
> Is it time to change the default to 24?
David/absolute -- www.NetBSD.org: No hype required --