ports/188431: Every python 2.7 port is generating broken .PLIST files
Kevin Thompson
antiduh at csh.rit.edu
Sat Apr 12 13:30:01 UTC 2014
The following reply was made to PR ports/188431; it has been noted by GNATS.
From: "Kevin Thompson" <antiduh at csh.rit.edu>
To: bug-followup at freebsd.org, william88 at gmail.com, xmj at freebsd.org,
koobs.freebsd at gmail.com
Cc:
Subject: Re: ports/188431: Every python 2.7 port is generating broken .PLIST
files
Date: Sat, 12 Apr 2014 09:24:59 -0400
> Well, of course it will break if you upgrade setuptools, our
> setuptools has a patch to handle a .PLIST issue with directories.
Could you elaborate? I was trying to follow instructions from
/usr/ports/UPDATING:
> 20140307:
> AFFECTS: users of devel/py-setuptools dependent ports
> AUTHOR: sunpoet at FreeBSD.org
> devel/py-setuptools is being used for every python ports (if
> USE_PYDISTUTILS
> defined) since r336553. Due to PKGORIGIN limitation, we cannot build
> one
> python port with python27 and the other with python33 since they
> require
> different setuptools versions which have same PKGORIGIN. With the
> addition
> of py-setuptools{27,32,33}, we could now have py27-foo and py33-bar
> coexist
> in one system.
> Note that this is only a short-term solution. It does not help if you
> need
> coexistence of one port with different python versions, e.g. py27-foo
> and
> py33-foo.
> Please rebuild all ports that depend on devel/py-setuptools and use
> devel/py-setuptools{27,32,33} instead.
> XX represents python version (27, 32 or 33) in the following steps.
> pkgng users:
> # pkg set -o devel/py-setuptools:devel/py-setuptoolsXX
> portmaster users:
> # portmaster -o devel/py-setuptoolsXX devel/py-setuptools
> # portmaster -r py\*setuptools
> portupgrade users:
> # portupgrade -o devel/py-setuptoolsXX -f devel/py-setuptools
> # portupgrade -fr devel/py-setuptools
More information about the freebsd-python
mailing list