We use the flat installation mode (e.g. no multiple versions by
default) by default. That avoids having to run DEINSTALL/INSTALL
scripts and allows DESTDIR installation.
Always prefer the default version and fallback to the first entry
of PYTHON_VERSIONS_ACCEPTED, which is supported by the current
system. Also honour PYTHON_VERSIONS_ACCEPTED and _INCOMPATIBLE,
when PYTHON_VERSION_REQD is used.
Python 2.4 is now in bugfix-only mode, no new features are being added. At
least 50 bugs have been squashed since Python 2.4.2, including a number of
bugs and potential bugs found by Coverity.
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
without underscores (REPLACE.*.old, REPLACE.*.new, and REPLACE_FILES.*).
Also convert REPLACE.*.new= ${SH:Q} back to ${SH}, as it should not be quoted
here, if at all.
Ok with rillig.
is not available for the platform.
Mark packages as "unavailable" instead of "broken" when they depend on
a python version that is not available for the platform.
by other package Makefiles, and with the deprecation of USE_BUILDLINK3
support in the infrastructure files, these had the potential to break
existing packages.
bin/python wrapper. Bump their PKGREVISION to 1.
Also remove the python package. In order to preserve a similar behavior to
this one using the new framework, start by installing pkg_alternatives.
Then just open its manpage, scroll down to the EXAMPLES section, Applying
filters subsection, and follow the (rather short) directions given there.
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
Note that this cannot be changed to ${INSTALL} because it is not the install
command but rather an argument to setup.py. While adding the quotes makes
no difference to the use of the file, it does keep pkglint quiet. This is
even more important because this file is included by many other packages
and causes warnings when trying to check new Python extensions.
by package Makefiles as well as buildlink3s to prevent usage of particular
versions of Python -- even if they appear in PYTHON_VERSIONS_ACCEPTED.
(And make Darwin exclusion use this variable instead, so that it effectively
overrides any pkg's definition of _ACCEPTED.)
