This is an updated port of Python-2.2.3, which includes some security fixes-- disabling the rexec and Bastion modules. I've included a patch which teaches the regression testing which modules are normally skipped on the "freebsd4" platform. I needed to patch /usr/ports/Mk/bsd.python.mk as well; diff is available in files/. It looks like someone spent a lot of time including stuff for backwards compatibility, so I left warnings from portlint in place: OK: checking /usr/ports/lang/python/pkg-descr. OK: checking Makefile. WARN: use of DISTFILES with single file discouraged. distribution filename should be set by DISTNAME and EXTRACT_SUFX. WARN: "LIB_DEPENDS" has to appear earlier in Makefile. WARN: DISTFILES/DISTNAME affects WRKSRC. take caution when changing them. OK: checking /usr/ports/lang/python/distinfo. OK: checking /usr/ports/lang/python/files/patch-Lib-test-regrtest.py. OK: checking /usr/ports/lang/python/files/patch-Modules-Setup.dist. OK: checking /usr/ports/lang/python/files/patch-setup.py. 0 fatal errors and 3 warnings found. Shar file included below. Fix: [ ...only send-pr aborted when I tried to send a ~130 K shar file... ] http://www.pkix.net/~chuck/python/ http://www.pkix.net/~chuck/python-port.shar How-To-Repeat: N/A
Responsible Changed From-To: freebsd-ports-bugs->alane Over to MAINTAINER
Responsible Changed From-To: alane->perky I'll handle it
State Changed From-To: open->closed The port is committed. I modified your patches in the following points: - you can't take a maintainership from this port. the current maintainer is active enough. - you can't change MAINTAINER?= to =. lang/python is a master port for lang/stackless_python. - unified diff against the current CVS is preferred than shar. - files on pkg-plist need to be sorted in alphabetical order. - your pkg-plist missed some files on %%PORTDOCS%%lib/%%PYTHON_VERSION%%/Tools. - %%PORTDOCS%% tags must be on the first of each lines. Thank you very much for your reporting!
Thanks for the commit. Re: the $MAINTAINER variable, "owning" the python port is not a concern. However, it is true that portlint states: WARN: unless this is a master port, COMMENT has to be set by "=", not by "?=". The term "master port" is not known to me, documented in "man portlint", or mentioned anywhere in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html Should portlint know whether a port is a "master port"? -- -Chuck