Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
Changes since Berkeley DB 4.4.16:
1. Add support for Visual Studio 2005. [#13521]
2. Fix a bug with in-memory transaction logs when files wrapped
around the buffer. [#13589]
3. Fix a bug where we needed to close replication's open files during
replication initialization. [#13623]
4. Fix a bug which could leave locks in the environment if database
compaction was run in a transactional environment on a non-transactional
database. This might have also have triggered deadlocks if the database
was opened transactionally. [#13680]
5. Fix a bug where setting the DB_REGISTER flag could result in
unnecessarily running recovery, or corruption of the registry file on
Windows systems. [#13789]
6. Fix a bug in Database.compact that could cause JVM crashes or
NullPointerException. [#13791]
7. Fix a bug that would cause a trap if an environment was opened
specifying DB_REGISTER and the environment directory could not be found.
[#13793]
8. Fix a buffer overflow bug when displaying process and thread IDs
in the Berkeley DB statistics output. [#13796]
9. Fix a bug where if there is insufficient memory for a database key
in a DBT configured to return a key value into user-specified memory, the
cursor is moved forward to the next entry in the database, which can cause
applications to skip key/data pairs. [#13815]
10. Fix a bug that could cause the loss of an update to a QUEUE database
in a hot backup. [#13823]
11. Fix a bug where retrieval from a secondary index could result in a
core dump. [#13843]
12. Fix a bug that could cause part of the free list to become unlinked
if a btree compaction was rolled back due to a transaction abort. [#13891]
13. Fix a bug with in-memory logging that could cause a race condition to
corrupt the logs. [#13919]
[no shlib major bump this time, yay]
|
|
New in Berkeley DB 4.4:
* In-memory replication
* Client-to-client replication
* Delayed client synchronization
* Synchronization throttling
* Master election speed-ups
* Hot backup utility
* Online Btree compaction
* Online Btree disk space reclamation
* Online abandoned lock removal
* Automated recovery serialization
* Transactional Application Developer's Guide
|
|
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
|
|
bits of "configure" that were twiddling only libtool-config bits, as these
are no longer used.
|
|
choose between link commands for shared or static linking.
Should fix shlib build and install on Interix.
|
|
4.3.28, so there are no API changes, and applications may be upgraded
by relinking against db4-4.3.29. We stop pretending to support a
"java" package option since we never even bothered with handling the
PLIST differences. Changes from version 4.3.28 include:
* The on-disk log format has changed.
* Add support for lightweight, transactionally protected Sequence
Number generation.
* Add support for Degree 2 isolation.
* Add election generation information to replication to support Paxos
compliance.
* A huge number of bug fixes, including eliminating some instances of
application deadlock and memory leak fixes.
* Some minor performance enhancements.
|
|
thus were before 2005Q3.
|
|
This is from Joerg Sonnenberger's diff.
I do not know if this support has been submitted to Sleepycat
for dist/configure* yet.
|
|
|
|
user settable variable. Set PKG_SUGGESTED_OPTIONS instead. Also,
make use of PKG_OPTIONS_LEGACY_VARS.
Reviewed by wiz.
|
|
The Announcement:
Berkeley DB 4.3.28 is a patch release to 4.3.27, everyone is encouraged
to update to this version. The following have been addressed in this
patch release:
1. All patches for the prior version have been applied as well
as a few other fixes.
2. The product is available as a Windows x86 binary installer
To see the change log for version 4.3.28, please visit:
http://www.sleepycat.com/updat e/4.3.27/if.4.3.27.html
|
|
|
|
|
|
|
|
|
|
versions define "__sgi", so use that.
This should fix PR pkg/28819.
|
|
Bump PKGREVISION.
|
|
* bug fixes
|
|
configure script still used -pthread during the POSIX mutex test even
when we explicitly disabled pthread through CONFIGURE_ENV, resulting
in re-enabling pthread.
Bump PKGREVISION.
|
|
* Automatic initialization of replication clients
* Replication election process is now Paxos compliant
* In memory transaction logs allowing in memory databases
* Enhanced Java API nearly identical to that of our Java Edition
* Native support for sequence number generation
* Degree 2 transaction isolation
* Mutex statistics can now be easily gathered and recorded
* Support for Itanium2 chips running Windows XP
|
|
the system as we don't need it.
|
|
non-GCC. DB4 uses its own code if we're using GCC instead of 1003.1
mutexes. Ride the previous PKGREVISION bump.
|
|
inter-process mutexes. In this case, we only care to use the native
threads. Bump the PKGREVISION since this means that non-native pthreads
platforms will no longer depend on GNU pth.
|
|
of relying on UNIX/fnctl, which can block all threads between processes
and cause certain mutex assumptions to fail.
|
|
pthread.buildlink3.mk higher before any target definitions to follow
package Makefile standards.
|
|
|
|
* Add a db1.builtin.mk file that detects whether DB-1.85 functionality
exists in the base system, and remove the distinction between
"native" and the other Berkeley DB packages -- we now refer to
db[1234]. This paves the way for any future databases/db1 package.
* USE_DB185 shouldn't need to be set by any packages -- its correct
value is now automatically determined by bdb.buildlink3.mk depending
on whether we explicitly request db1 or not. By default, if you
include bdb.buildlink3.mk, you want DB-1.85 functionality and
USE_DB185 defaults to "yes", but if you explicitly remove db1 from
the list of acceptable DBs, then USE_DB185 defaults to "no".
* Set BDB_LIBS to the library options needed to link against the DB
library when bdb.buildlink3.mk is included.
* We only add the DB library to the linker command automatically if
we want DB-1.85 functionality; otherwise assume that the package
configure process can figure out how to probe for the correct
headers and libraries.
Edit package Makefiles to nuke redundant settings of USE_DB185.
|
|
|
|
Sleepycat instead of patch-ba and patch-bb. Since patch-ba was actually
an incomplete version of patch.4.2.52.1, we bump the PKGREVISION.
|
|
|
|
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.
|
|
files and symlinks mistakenly removed.
|
|
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".
|
|
intended transformation: use "rm" to remove an option, "rmdir" to remove
all options containing a path starting with a given directory name, and
"rename" to rename options to something else.
|
|
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
|
|
implementation.
|
|
|
|
1. Long-running applications can hang in the Berkeley DB cache.
http://www.sleepycat.com/update/4.2.52/patch.4.2.52.1 as patch-ba
2. Replication clients fail to lock all the necessary pages when
applying updates if there were more than one database in the transaction.
http://www.sleepycat.com/update/4.2.52/patch.4.2.52.2 as patch-bb
Bump PKGREVISION to 4.
|
|
|
|
PKGREVISION due to user-visible difference.
|
|
resolve all symbols. bump PKGREVISION.
fixes PR pkg/24720.
|
|
|
|
using -ldb4 alone don't complain about missing symbols. This fixes the
build of some programs (like evolution-data-server), as exposed in Linux.
|
|
non-standard location. Also match the new USE_DB185 behaviour where it
defaults to "yes".
|
|
names for the newer Sleepycat DB libraries.
|
|
|
|
|
|
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
|