Re: Retstricting versions/builds with pkgtools

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Fri, 17 Sept 2021 at 22:16, Todd Gruhn <tgruhn2%gmail.com@localhost> wrote:
>
> I noticed that I often get Python checked and/or installed when I
> build software.
>
> I currently have 3 versions of Python on my system.
>
> If the package requires Python-2.7, how well will it work if
> Python-3.8 is already
> installed? Can I tell pkgtools to skip installing Python if a certain ver of
> Python is already installed? Is this advisable?

If a package requires specifically python version 2.7, it will be
installed, as well as all the relevant modules; you may have already,
say, PYTHON_VERSION_DEFAULT=39 in /etc/mk.conf, but if a package
specifies another version, it will get it. Usually there are no
problems with this, except when a package installs executables without
the version of python appended to the name.

I recently switched my primary development machine from python3.7 to
3.9, replacing all modules and rebuilding all packages requiring
python v.3, it took me some time, but eventually I was able to remove
python38 and python37, I am left at the moment only with python27 and
39. There are still quite a few packages with PYTHON_VERSIONS_ACCEPTED
= 27.


-- 
----