ports/lang/python25/Makefile, branch release/8.0.0

- Ask the first Python installed to install the bin/python link,

2009-07-14T09:29:03Z

and be the default Python version PR: ports/109550 Submitted by: David Yeske Obtained from: tmclaugh

- Honor EXAMPLESDIR, DATADIR, NOPORTEXAMPLES, NOPORTDATA

2009-07-12T17:17:26Z

- Update lang/python26 and make Python 2.6.2 to the default Python version

2009-06-08T22:30:55Z

Tested by: 3 pointyhat runs Thanks to: pav, gahr, lwhsu, mva, amdmi3

Make sure the singal is delivered to the main thread, where python

2009-02-27T01:25:32Z

runs its signal handlers, not to a random thread that happens to be executing at the time when signal arrives. This functionality has been lost since Python 2.3, possible cause is that the linux implementation of POSIX threads always delivered signal to the main thread. This bug results in rather annoying inability to terminate threading script with ^C for example and there could be other issues as well. Bump PORTREVISION. PR: ports/131080 Submitted by: Andriy Pylypenko Approved by: MAINTAINER's timeout

- Update to python 2.5.4 and python 2.6.1

2009-02-16T23:32:02Z

Reviewed by: perky | lwhsu Tested with: exp-run via pav

- Security fixes

2008-09-08T00:14:06Z

Multiple vulnerabilities: 1) Various integer overflow errors exist in core modules e.g. stringobject, unicodeobject, bufferobject, longobject, tupleobject, stropmodule, gcmodule, mmapmodule. 2) An integer overflow in the hashlib module can lead to an unreliable cryptographic digest results. 3) Integer overflow errors in the processing of unicode strings can be exploited to cause buffer overflows on 32-bit systems. 4) An integer overflow exists in the PyOS_vsnprintf() function on architectures that do not have a "vsnprintf()" function. 5) An integer underflow error in the PyOS_vsnprintf() function when passing zero-length strings can lead to memory corruption. PR: 127172 (based on) Submitted by: bf Obtained from: python svn Security: CVE-2008-2315, CVE-2008-2316, CVE-2008-3142, CVE-2008-3144, CVE-2008-3143. (vuxml come later)

Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.

2008-08-21T06:18:49Z

Specifically, newer autoconf (> 2.13) has different semantic of the configure target. In short, one should use --build=CONFIGURE_TARGET instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning and the old semantic may be removed in later autoconf releases. To workaround this issue, many ports hack the CONFIGURE_TARGET variable so that it contains the ``--build='' prefix. To solve this issue, under the fact that some ports still have configure script generated by the old autoconf, we use runtime detection in the do-configure target so that the proper argument can be used. Changes to Mk/*: - Add runtime detection magic in bsd.port.mk - Remove CONFIGURE_TARGET hack in various bsd.*.mk - USE_GNOME=gnometarget is now an no-op Changes to individual ports, other than removing the CONFIGURE_TARGET hack: = pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables) - comms/gnuradio - science/abinit - science/elmer-fem - science/elmer-matc - science/elmer-meshgen2d - science/elmerfront - science/elmerpost = use x86_64 as ARCH - devel/g-wrap = other changes - print/magicfilter GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf Total # of ports modified: 1,027 Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes) PR: 126524 (obsoletes 52917) Submitted by: rafan Tested on: two pointyhat 7-amd64 exp runs (by pav) Approved by: portmgr (pav)

- Fix zlib crash from zlib.decompressobj().flush(val)

2008-04-25T08:16:04Z

when val was not positive. It tried to allocate negative or zero memory. That fails. - Bump PORTREVISION Reviewed by: alexbl Obtained from: python svn Security: http://www.vuxml.org/freebsd/ec41c3e2-129c-11dd-bab7-0016179b2dd5.html

- Remove unneeded dependency from gtk12/gtk20 [1]

2008-04-19T17:56:05Z

- Remove USE_XLIB/USE_X_PREFIX/USE_XPM in favor of USE_XORG - Remove X11BASE support in favor of LOCALBASE or PREFIX - Use USE_LDCONFIG instead of INSTALLS_SHLIB - Remove unneeded USE_GCC 3.4+ Thanks to all Helpers: Dmitry Marakasov, Chess Griffin, beech@, dinoex, rafan, gahr, ehaupt, nox, itetcu, flz, pav PR: 116263 Tested on: pointyhat Approved by: portmgr (pav)

- Fix plist

2008-02-25T16:39:19Z

Reported by: pointyhat