summaryrefslogtreecommitdiff
path: root/databases/gdbm
AgeCommit message (Collapse)AuthorFilesLines
2017-03-20Version 1.13 - 2017-03-11adam7-15/+33
* 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.
2016-05-22Version 1.12, 2016-05-16wiz8-103/+7
* New configuration variable COMPATINCLUDEDIR When used with --enable-libgdbm-compat, this variable points to the directory where the headers file dbm.h and ndbm.h will be installed. Use this variable to avoid conflicts with already installed headers. E.g.: ./configure --enable-libgdbm-compat COMPATINCLUDEDIR=/usr/include/gdbm
2015-11-03Add SHA512 digests for distfiles for databases categoryagc1-1/+2
Problems found with existing distfiles: distfiles/D6.data.ros.gz distfiles/cstore0.2.tar.gz distfiles/data4.tar.gz distfiles/sphinx-2.2.7-release.tar.gz No changes made to the cstore or mariadb55-client distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2014-10-09Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.wiz1-3/+1
2014-05-23Add patches needed for gdbm-1.11.wiz6-0/+90
2014-05-23Update gdbm packages to 1.11, after martin@ diagnosed the compilationwiz4-10/+25
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.
2013-11-23Use find-headers instead of find-files to detect builtin header files.obache1-3/+3
2013-04-08Remove "Trailing empty lines." and/or "Trailing white-space."rodent1-2/+1
2012-10-02Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.asau1-2/+1
2012-01-24Use the correct version number for BUILDLINK_ABI_DEPENDS.gdbmsbd1-2/+2
2012-01-24Add gettext-lib buildlink to gdbm's buildlink3.mksbd1-2/+4
Bump ABI_DEPENDS
2012-01-24Pullin gettext-lib buildlink3 so that nls files are built.sbd2-14/+9
Unconditionalise the nls files. Bump PKGREVISION
2012-01-24Fo gdbm 'NLS' seems to mean 'can find _nl_expand_alias', which has aabs2-8/+17
certain Linux flavour to it. Conditionalise the nls files in the PLIST to Linux for now Bump PKGREVISION. Fixes build on at least NetBSD
2012-01-23Add missing LC_MESSAGES files.sbd2-2/+8
Bump PKGREVISION
2012-01-08Changes 1.10:adam2-6/+6
* Internationalization This version of GDBM is fully internationalized. The following localizations are available: Finnish, German, Japanese, Polish and Ukrainian. * Support for close-on-exec flag in gdbm_open (see GDBM_CLOEXEC in the docs). * Improve testgdbm command system The testgdbm tool now supports multicharacter commands. * Bugfixes
2011-12-03Add builtin.mk files for databases/gdbm and databases/gdbm_compatsbd1-0/+69
2011-10-17split up Makefile.obache2-9/+21
2011-10-17gdbm-1.9 is GPLv3.obache1-2/+2
2011-08-23Recursive bump from gdbm shlib bump.obache1-2/+2
2011-08-17Changes 1.9.1:adam4-89/+11
* 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.
2010-01-24Added LICENSE information.heinz1-1/+2
2009-09-02Always use --mode for libtool.joerg2-8/+42
2009-03-20Simply and speed up buildlink3.mk files and processing.joerg1-13/+6
This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2007-08-26The package supports installation to DESTDIR (although it uses theheinz1-1/+3
variable INSTALL_ROOT).
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-03-30* Honor PKGINFODIR.jlam2-3/+4
* List the info files directly in the PLIST.
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
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.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-2/+4
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.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-5/+1
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".
2004-05-14Unused.wiz1-19/+0
2004-05-02Enable pkgviews installation.minskim1-1/+3
2004-03-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-3/+5
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-02-14remove unneeded CONFIG_{GUESS,SUB}_OVERRIDE, as bsd.pkg.mk does thisgrant1-3/+1
automatically now.
2004-02-12bl3ifyjlam2-2/+18
2004-01-20Remove info files entries from PLIST files.seb1-2/+1
2003-08-09USE_NEW_TEXINFO is unnecessary now.seb1-2/+1
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-29Convert to USE_NEW_TEXINFO.seb2-9/+3
Note: distributed gdbm.info now has a *DIR-{SECTION,ENTRY} hence post-extract target no more required.
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2002-11-01Remove patch file obsoleted by last update of this package.tron1-14/+0
2002-11-01Update to 1.8.3:wiz5-44/+30
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.
2002-10-10Unused.jlam1-34/+0
2002-09-11Build on Darwin:schmonz3-10/+40
* don't pass a second (and wrong) pair of -o and -u arguments to ${INSTALL} * use canonical pkgsrc config.guess and config.sub
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam3-3/+22
buildlink2.mk files back into the main trunk. This provides sufficient buildlink2 infrastructure to start merging other packages from the buildlink2 branch that have already been converted to use the buildlink2 framework.