Age | Commit message (Collapse) | Author | Files | Lines |
|
releases is enough" rule of thumb. (python 2.3 was released 5 years ago.)
Keep python 1.5 and 2.1 though, because there are a handful of packages
that still need them.
|
|
stages in the future. Suggested by rillig@
|
|
|
|
Patch provided by Sergey Svishchev in private mail.
|
|
|
|
on DragonFly. Since that version is used e.g. as part of the file name
for python eggs, it makes handling easier to match normal pkgsrc
platform policy. Bump revisions of all Python packages.
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in
http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
|
|
This is needed for databases/py-psycopg at least to compile properly.
Since the installed version changed, bump revision.
|
|
library) from ubuntu Linux (via gentoo).
For details see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2491
|
|
|
|
http://www.python.org/security/PSF-2005-001/
This disables hierarchical object lookups in SimpleXMLRPCServer.
Unfortunately, this breaks some applications (eg kenosis). Don't
shoot me for this.
bump PKGREVISION
|
|
bin/python wrapper. Bump their PKGREVISION to 1.
Also remove the python package. In order to preserve a similar behavior to
this one using the new framework, start by installing pkg_alternatives.
Then just open its manpage, scroll down to the EXAMPLES section, Applying
filters subsection, and follow the (rather short) directions given there.
|
|
modules into the other PLIST fragments.
|
|
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
|
|
Bump PKGREVISIONS accordingly.
|
|
python20 to python20-2.0.1nb6
python21 to python21-2.1.3nb2
python21-pth to python21-2.1.3nb4
python22 to python22-2.2.3nb1
python22-pth to python22-2.2.3nb1
python23 to python23-2.3.3nb1
python23-pth to python23-2.3.3nb1
|
|
and fix PLIST for some modules which are only installed on Solaris.
|
|
|
|
environment
|
|
This is a bugfix release.
Also, use the LINK_ALL_LIBGCC_HACK just introduced to link the
interpreter against libgcc. This should fix PR pkg/16144 in the
Python2.2 (and NetBSD-1.5) case.
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
|
|
by py-bsddb3) since the PR has been closed. Two other issues remain.
|
|
|
|
Before using native pthreads per default, we should make sure it is
at least stable enough for the Python selftests and pkgsrc applications.
(in response to PR pkg/20214)
|
|
XXX only python22 pkg is changed this way, since this is the only
XXX one having special case for NetBSD; python15, python20, python21 disable
XXX threads on all pkgsrc operating systems
|
|
|
|
|
|
|
|
Mostly bug fixes, a few enhancements, notably in the email package.
|
|
nned for the updated patch in the previous commit) and the empty
"PLIST_SRC+=" was kinda silly.
|
|
|
|
|
|
Changes:
-Added new builtin function bool() and new builtin constants True and
False to ease backporting of code developed for Python 2.3. In 2.2,
bool() returns 1 or 0, True == 1, and False == 0.
-C API: A type can now inherit its metatype from its base type.
-Fixes
|
|
LDFLAGS to the linker command when linking a python extension. This lets
us pass the right flags to correctly find libraries required for certain
extensions, e.g. zlib.so.
|
|
|