On Tue, Jan 31, 2012 at 05:37:54PM -0800, Paul Hoffman wrote:
> ftp.freebsd.org: /pub/FreeBSD/ports/i386/packages-8.2-release/All
We don't update ports in the *-release directories once the release
has been cut. Our recommendation is that you should always keep your
ports tree up-to-date, and dow
2012/2/1 Mark Linimon
> On Tue, Jan 31, 2012 at 04:24:24PM -0800, Paul Hoffman wrote:
> > Nearly all of the packages in the packages system for Python-related
> > ports are for Python 2.6 *only*.
>
Maybe you should check your /etc/make.conf , do you set default python
version to 2.6 ?
wen
>
On Jan 31, 2012, at 5:11 PM, wen heping wrote:
> Maybe you should check your /etc/make.conf , do you set default python
> version to 2.6 ?
I'm talking about packages in the FreeBSD packages repository, not ports I
build on my box.
--Paul Hoffman___
f
On Jan 31, 2012, at 4:45 PM, Mark Linimon wrote:
> On Tue, Jan 31, 2012 at 04:24:24PM -0800, Paul Hoffman wrote:
>> Nearly all of the packages in the packages system for Python-related
>> ports are for Python 2.6 *only*.
>
> er, you'll have to tell me where you're seeing this?
ftp.freebsd.org:
On Tue, Jan 31, 2012 at 04:24:24PM -0800, Paul Hoffman wrote:
> Nearly all of the packages in the packages system for Python-related
> ports are for Python 2.6 *only*.
er, you'll have to tell me where you're seeing this?
I checked on pointyhat, on a recent i386-8 build for 8-STABLE:
$ pwd
/dum
OK, so that last one went nowhere, let me try a more general topic. Nearly all
of the packages in the packages system for Python-related ports are for Python
2.6 *only*. Those packages cannot be applied to Python 2.7 or Python 3.x.
Is there a good reason for this, particularly in light of the mu
