Changelog:
Changes between 1.3.1 and 1.4.0
-------------------------------
070708 o upgraded GNU shtool from 2.0.3 to 2.0.7
o adjusted year range in copyright messages
o upgraded build environment to GNU autoconf 2.61
Changes between 1.3.0 and 1.3.1
-------------------------------
051005 o upgraded GNU shtool from 2.0.1 to 2.0.3
o adjusted year range in copyright messages
Changes between 1.2.0 and 1.3.0
-------------------------------
040911 o upgraded GNU shtool from 1.6.2 to 2.0.1
o upgraded build environment to GNU autoconf 2.59
200404 o upgraded GNU shtool from 1.6.0 to 1.6.2
o fixed years in copyright
2002xx o upgraded GNU shtool from 1.5.0 to 1.6.0
o fixed years in copyright
2000xx o upgraded GNU shtool from 1.3.0 to 1.5.0
o fixed years in copyright
990530 o fixed iselect.pod: %s[ -> %[
990622 o fixed type conversion [Mark A. Hershberger <mah@everybody.org>]
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.
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.
Iselect is a curses based interactive selection tool. It can be used
either as an user interface frontend controlled by a
Bourne-Shell/Perl/Tcl backend as its wrapper or in batch mode as a
pipeline filter (usually between grep and the final executing command).
