Re: how to enforce one version of python
On Tue, Sep 11, 2018 at 03:28:15PM +0100, tech-lists wrote: > Hi, > > There are a number of ports that seem to have their own preferential flavour > of python, and some for example want to install python27 and python36 in the > same place, and it's a pain when using portupgrade or similar tools. > > I have this in my /etc/make.conf: > > DEFAULT_VERSIONS+= python=2.7 > > Is this incorrect? I assume it must be, as for example devel/pylint > (pylint-py27-1.9.2) wants to upgrade to pylint-py36-2.1.1 > That is because portupgrade is not flavor aware (or badly if it has been patched to support flavors) Best regards, Bapt signature.asc Description: PGP signature
how to enforce one version of python
Hi, There are a number of ports that seem to have their own preferential flavour of python, and some for example want to install python27 and python36 in the same place, and it's a pain when using portupgrade or similar tools. I have this in my /etc/make.conf: DEFAULT_VERSIONS+= python=2.7 Is this incorrect? I assume it must be, as for example devel/pylint (pylint-py27-1.9.2) wants to upgrade to pylint-py36-2.1.1 thanks, -- J. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
