Up to [cvs.NetBSD.org] / pkgsrc / databases / gdbm
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
databases/{gdbm,gdbm_compat}: Update to 1.24
Changelog:
1.24:
New gdbm_load option: --update
The --update (-U) option instructs gdbm_load to update an existing database.
Fix semantics of gdbm_load -r
The --replace (-r) is valid only when used together with --update.
Use getline in gdbmtool shell
New function: gdbm_load_from_file_ext
In contrast to gdbm_load and gdbm_load_from_file, which derive the value of the flag parameter for gdbm_open from the value of their replace argument, this function allows the caller to specify it explicitly.
Bugfixes
* Fix binary dump format for key and/or data of zero size (see bug #565)
* Fix location tracking and recover command in gdbtool (see bug #566)
* Fix possible buffer underflow in gdbmload.
* Ensure any padding bytes in avail_elem structure are filled with 0. This fixes https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031276.
* Improve the documentation
Add option "nls" enabled by default
gdbm: update to 1.19.
Version 1.19 - 2020-12-23
* Pre-read the memory mapped regions on systems that support it.
This speeds up operations on big databases.
* gdbmtool: tagged initialization of structured data
Initializers for structured data can be given in tagged form, e.g.:
store somekey { status=2, id={a,u,x}, name="foo" }
* Bugfixes:
** Preserve locking type during database reorganization
gdbm: update to 1.18.1. Version 1.18.1 - 2018-10-27 * Fix debian bug 910911 This restores backward compatibility with databases created by version 1.8 (and some later versions, with mmapped I/O disabled). See https://bugs.debian.org/910911 for a detailed description. Version 1.18 - 2018-08-21 * Bugfixes: ** Fix directory entry validation See https://puszcza.gnu.org.ua/bugs/?402 Directory validation function would falsely report corruption after several directory reallocations. ** Fix improper use of GDBM_DEBUG macro See https://puszcza.gnu.org.ua/bugs/?401 ** Fix spurious error from gdbm_dump and gdbm_export The functions incorrectly reported as error the GDBM_ITEM_NOT_FOUND status, which is reported when upon normal termination of iteration over the database keys. ** Make sure gdbm_sync always returns a meaningful value See https://puszcza.gnu.org.ua/bugs/?400 Version 1.17 - 2018-07-30 * int gdbm_close and gdbm_sync Both functions now return 0 on success. On error, they return -1 and set gdbm_errno and errno to the appropriate error codes. * Fix bug in gdbm_dump function The function did not clear the GDBM_ITEM_NOT_FOUND error marker, which is set upon its normal termination. Version 1.16 - 2018-06-27 * Maintain sorting order of the available block list after coalescing This is a very long-standing bug, dated back to the time when optional coalescing of available blocks with the newly released block was introduced. Merging the released block with an adjacent block of available space would clobber the sorting order of the available list. The bug was discovered due to strict database consistency checks, introduced in version 1.15. The fix introduced in this version will silently restore the proper sorting order of available block list before its use. * Improve block merging algorithm New implementation of block merging algorithm will correctly handle both left and right-adjacent blocks. Version 1.15 - 2018-06-15 * Extensive database consistency checking GDBM tries to detect inconsistencies in input database files as early as possible. When an inconcistency is detected, a helpful diagnostics is returned and the database is marked as needing recovery. From this moment on, any GDBM function trying to access the database will immediately return error code (instead of eventually segfaulting as previous versions did). In order to reconstruct the database and return it to healthy state, the gdbm_recover function should be used. Special thanks to Lionel Debroux and Craig Young for investing their time and efforts in testing and providing valuable feedback. * Improved error checking * Removed gdbm-1.8.3 compatibility layer * Commands can be given to gdbmtool in the command line The syntax is: gdbmtool DBNAME COMMAND [ARGS...] Multiple commands are separated by semicolon (take care to escape it), e.g.: gdbmtool t.db count\; avail * Fixed data conversion bugs in storing structured keys or content * New member in the gdbm_recovery structure: duplicate_keys. Upon return from gdbm_recover, this member holds the number of keys that has not been recovered, because the same key had already been stored in the database. The actual number of stored keys is thus recovered_keys - duplicate_keys. * New error codes. GDBM_BAD_BUCKET "Malformed bucket header" GDBM_BAD_HEADER "Malformed database file header" GDBM_BAD_AVAIL "Malformed avail_block" GDBM_BAD_HASH_TABLE "Malformed hash table" GDBM_BAD_DIR_ENTRY "Invalid directory entry"
Version 1.13 - 2017-03-11 * gdbm_fetch, gdbm_firstkey, and gdbm_nextkey behavior If the requested key was not found, these functions return datum with dptr pointing to NULL and set gdbm_errno to GDBM_ITEM_NOT_FOUND (in prior releases, gdbm_errno was set to GDBM_NO_ERROR), If an error occurred, dptr is set to NULL, and gdbm_errno to the error code. In any case gdbm_errno is guaranteed to have meaningful value upon return. * Error handling In previous versions of GDBM, fatal errors (such as write error while storing the key/data pair or bucket) caused immediate termination of the program via call to exit(3). This is no longer the case. Starting from this version, if a fatal error occurrs while modifying the database file, that database is marked as needing recovery and gdbm_errno is set to GDBM_NEED_RECOVERY. Calls to any GDBM functions, except gdbm_recover, will then return immediately with the same error code. The function gdbm_recover examines the database file and fixes eventual inconsistencies. Upon successful return it clears the error state and makes the database operational again. For backward compatibility, the fatal_func argument to gdbm_open is retained and its functionality is not changed. If it is not NULL, the new error handling procedures are disabled, the function it points to will be called upon fatal errors. When it returns, exit(1) will be called. * Per-database error codes In addition to gdbm_error global variable, the most recent error state is saved in the GDBM_FILE structure. This facilitates error handling when operating multiple GDBM databases simultaneously.
Update gdbm packages to 1.11, after martin@ diagnosed the compilation
problem. Thanks, martin!
Changes:
Version 1.11, 2013-12-25
* Improved dump format.
A new dump format is implemented, which encodes all data in base64 and
stores not only key/data pairs, but also the original database file
metadata, such as file name, mode and ownership. Files in this format
can be sent without additional encapsulation over transmission
channels that normally allow only ASCII data. Dumps in this format
allow for restoring an exact copy of the database, including file
ownership and privileges.
* New function: gdbm_count
int gdbm_count (GDBM_FILE *file, gdbm_count *count);
Counts records in `file' and stores the result in the memory location
pointed to by `count'.
* New utilities: gdbm_dump and gdbm_load.
Gdbm_dump creates a plain-text dump of the GDBM database. This dump
can be used to create an exact copy of the database afterward.
The gdbm_load performs the reverse: given the dump file, it creates a
GDBM database. Apart from native GDBM dump formats, it also understands
the format generated by Berkeley DB db_dump utility. Thus, an easy
way to convert a Berkeley DB database to GDBM is:
db_dump input.db | gdbm_load output.db
* gdbmtool
The gdbmtool utility allows you to examine, modify or create GDBM
databases. It provides an easy-to-use interactive shell and can
be used for scripting. One of the unique features of gdbmtool is that
it allows to define datum structures for key and content parts, similarly
to the C "struct" declarations, and to input and display such
structured data.
Pullin gettext-lib buildlink3 so that nls files are built. Unconditionalise the nls files. Bump PKGREVISION
Fo gdbm 'NLS' seems to mean 'can find _nl_expand_alias', which has a certain Linux flavour to it. Conditionalise the nls files in the PLIST to Linux for now Bump PKGREVISION. Fixes build on at least NetBSD
Add missing LC_MESSAGES files. Bump PKGREVISION
Changes 1.9.1: * Bugfix: Improperly used preprocessor directive caused compilation failure when using gcc 4.4.4 or newer. Changes 1.9: * Use of mmap * Changes in compatibility mode * Locking is disabled. * Do not link pag to dir. * gdbm_setopt * The testgdbm program is installed * A testsuite is provided. * Improved documentation.
* Honor PKGINFODIR. * List the info files directly in the PLIST.
Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST. 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".
Remove info files entries from PLIST files.
Convert to USE_NEW_TEXINFO.
Note: distributed gdbm.info now has a *DIR-{SECTION,ENTRY} hence
post-extract target no more required.
Update to 1.8.3: CHANGES from 1.8.2 to 1.8.3 1. Various configure related changes and additional updates. CHANGES from 1.8.1 to 1.8.2 1. Allow `NEWDB'-opened databases to actually, well, store records. CHANGES from 1.8 to 1.8.1 1. Lots of bug fixes, including a data corruption bug. 2. Updated to current autoconf and libtool. 3. Moved the dbm/ndbm compatibility routines to libgdbm_compat.
Introduce new framework for handling info files generation and installation.
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
removal of USE_GTEXINFO
INSTALL_INFO added to PLIST_SUBST
`${INSTALL_INFO}' replace `install-info' in target rules
print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
makeinfo command usage
See -newly added by this commit- section 10.24 of Packages.txt for
further information.
Move pkg/ files into package's toplevel directory