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.
|
|
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
|
|
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
|
|
|
|
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.
|
|
that they look nicer.
|
|
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
|
|
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.
|
|
Use PTHREAD_* instead of hardcoded -lpthread.
|
|
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.
|
|
needed as well. This is especially the case when
lib/pythonXconfig/Makefile is used as done e.g. www/ap2-python.
|
|
library) from ubuntu Linux (via gentoo).
For details see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2491
|
|
structure padding is used
not application relevant, so I abstain from bumping PKGREVISION
|
|
|
|
|
|
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.
|
|
|
|
|
|
python23.
|
|
|
|
Bump PKGREVISIONS accordingly.
|
|
ok'd a while back at pkgsrcCon by agc and wiz
|
|
|
|
python2[12]{,-pth} build on platforms where zlib.h is not in
/usr/include.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
and any pre-existing buildlink2.mk files.
|
|
|
|
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
|
|
* Use BUILDLINK_{INCDIRS,LIBDIRS}.<pkg> instead of using
BUILDLINK_{CPPFLAGS,LDFLAGS}.<pkg> since we're just dealing with adding
directories to the various search paths.
|
|
|
|
|
|
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.
|
|
succeeds on alpha
|
|
|
|
|