in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
curses.buildlink2.mk. This was wrong because we _really_ do want to
express that we want _n_curses when we include the buildlink2.mk file.
We should have a better way to say that the NetBSD curses doesn't
quite work well enough. In fact, it's far better to depend on ncurses
by default, and exceptionally note when it's okay to use NetBSD curses
for specific packages. We will look into this again in the future.
extension Makefile fragments, because they really don't have anything to
do with the buildlink[12] frameworks. Change all the Makefiles that use
application.buildlink.mk and extension.buildlink.mk to use application.mk
and extension.mk instead.
newer Python versions too,
XXX we have to override the do-patch rule to avoid patch errors
(we use EXTRACT_ELEMENTS, so we don't generally have all the
original files)
lang/python upgraded to 2.0
lang/py-html-docs upgraded to 2.0
misc/py-readline upgraded to 2.0
databases/py-gdbm upgraded to 2.0
x11/py-Tk upgraded to 2.0
devel/py-curses upgraded to 2.0
lang/py-extclass upgraded to 2.2.2 and for Python 2.0
textproc/py-dtml upgraded to 2.2.2 and for Python 2.0
www/py-zpublisher upgraded to 2.2.2 and for Python 2.0
print/py-reportlab upgraded to 1.01 and for Python 2.0
More coming...
- New, optional Makefile variable HOMEPAGE, specifies a URL for
the home page of the software if it has one.
- The value of HOMEPAGE is used to add a link from the
README.html files.
- pkglint updated to know about it. The "correct" location for
HOMEPAGE in the Makefile is after MAINTAINER, in that same
section.
