Summary: | Update port: lang/python to 2.2.3 [security] | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Chuck Swiger <chuck> |
Component: | Individual Port(s) | Assignee: | Hye-Shik Chang <perky> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | alane |
Priority: | Normal | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Chuck Swiger
2003-06-01 03:00:29 UTC
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 |