built with python versions previous to 2.6.
- Simplify MODPY_BADEGGS.
- Fake setuptools if MODPY_SETUPTOOLS is not present to detect those ports
that will build regardless but the resulting plist will be different.
Input, tested and ok by many, thanks!
MULTI_PACKAGES, and add an (ONLY|NOT)_FOR_ARCHS-subpkg=somearch, rather
than changing contents of the MULTI_PACKAGES variable.
Fixes dpb builds on !amd64/i386, because the bsddb package was
knocked out on other arch.
'please unfuck the fucking mess people only testing on i386 and
amd64 did' landry@
so work around by tricking it to write into WRKINST through a symlink.
keep this here, so that affected ports need minimal modifications, and we
can work out a better fix long term.
Agreed with wcmaier...
by jasper@'s fixes to the libffi port.
Mark mips64 (aka, sgi) as BROKEN, as the build fails. We'll look closer
at this after unlock.
OK jasper@
ports is unlocked for a while only for those who have been informed.
breaking cd /usr/ports && SUBDIR=some/path make something for
category makefiles. While there, also put spaces around += uniformously.
okay naddy@, jasper@
Lots of python ports already do this, so better factorize. It will also
help mitigate some build breakages when several python versions are
installed.
Related ports cleanup coming in a few...
"looks ok" wcmaier@
"makes sense" sthen@
"no objection" djm@
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
- idle was incorrectly included in the -main package, not the -idle
subpackage. Move these to where they belong.
- The -main package installed a ${LOCALBASE}/python-config, which
would conflict with future python versions. Remove this and add
a MESSAGE suggesting users symlink python-config2.5 to it if
necessary
- An Emacs .el files was also installed by the -main package, this
too would conflict with parallel installs of different major
releases. Move this to the -tools subpackage.
bump PKG_PATCHLEVEL
Flip default ALL_TARGET to the one that will be used for current
and future (>=2.5) Python releases, move old default down into
2.3 and 2.4 Makefiles
Turn on a verbose retry when regress tests fail; saves messing with
LD_LIBRARY_PATH incantations to get them to rerun
Take maintainership
CVE-2008-1679 CVE-2008-1721 CVE-2008-1887
CVE-2008-2316 CVE-2008-3142 CVE-2008-3144
Patches cherrypicked with assistance of val.masutin AT gmail.com and
Toni Mueller.
Tested by sthen@ naddy@ ok pvalchev@
