Successfully tested with gnome which is the biggest consumer of py3 -- any
regression, please let me know.
discussed with fgsch@ rpointel@ sthen@ jasper@ landry@ zhuk@
automatically change from scripts from using /usr/bin/env python or
/usr/bin/python to using #!${MODPY_BIN} .
Add a MODPY_ADJ_FILES in which you can put the files that are under
${WRKSRC} you want to subtitute the shebang.
e.g.
MODPY_ADJ_FILES= setup.py bin/foobar.py.in
Some input from djm@
"sane idea to me" jasper, ok sthen@
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!
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...
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@
Previously, when eg MODPY_VERSION is a substring of a variable added
to SUBST_VARS in a port's Makefile, pain on update-plist can ensue.
Makes updates on www/py-django more fun. Tests and feedback from
merdely@ and Darrin Chandler; thanks!
ok steven@, "if it doesn't break anything..." fgsch@
This'll prevent setuptools from creating egg-info filenames
encoded with the package version (even when MODPY_SETUPTOOLS
isn't enabled).
ok mbalmer@, eric@, merdely@; input from many py porters
ajacoutot