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.
rather than PKG_FAIL_REASON, so that they provide useful error
messages in build logs, and so that they continue to work on platforms
where they aren't broken.
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.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
- Fix a bug where calling the env.log_put method caused a core dump. [#3401]
- Fix a bug where the Java lock statistics structure was out-of-date with
the C version and the documentation. [#3489]
- Use distfile and patches/* from ../db3
- Updated version to 3.2.9.2
- Apply two patches from the master distribution site
3.2.9.1 Fix a bug where running recovery on a database environment
containing only logs from a previous release of Berkeley DB,
in which log.0000000001 doesn't exist, could fail.
3.2.9.2 Fix a bug where opening too many files causes a core dump.
