From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-sources@gnu.org
Cc: guile-user@gnu.org
Subject: Guile-GDBM 1.1.0 available
Date: Mon, 12 Aug 2013 20:50:31 +0200 [thread overview]
Message-ID: <878v06hhfs.fsf@zigzag.favinet> (raw)
[-- Attachment #1: Type: text/plain, Size: 3078 bytes --]
release notes:
Got tired of waiting for Debian, and installed GNU dbm 1.10 under
/usr/local; naturally, Guile-GDBM must follow suit.
thi
README excerpt:
Guile-GDBM is a Guile module that provides Scheme bindings to the
GNU dbm library. It was originally written by Martin Grabmüller
and is now released under the GNU General Public License (GPL)
version 3.
Guile-GDBM has been tested with Guile 1.4.x, 1.8.7, 2.0.9,
and GNU dbm 1.8.3, 1.10.
NEWS excerpt:
- 1.1.0 | 2013-08-03
- bug-report address changed
Please send bug reports to the address shown by running command:
./configure --help
Mail sent to the previous address is likely to be misplaced.
- support for GNU dbm 1.10
GNU dbm 1.9 (released 2011-08-12) added several "mode flags" and
runtime options; GNU dbm 1.10 (released 2011-11-13) added the
close-on-exec mode flag. These are now fully supported, if you
build Guile-GDBM against one of those versions (see following
NEWS entries for details).
Building against GNU dbm 1.8.3 (released 2002 or thereabouts) is
still supported, but of course functionality is degraded. There
is no plan to remove this support in the Guile-GDBM 1.x series.
- ‘gdbm-open’ MODE can include flags
Previously, the MODE arg was a simple symbol. Now it can also
be the form: ‘(MODE [FLAG...])’, where FLAG is from the set:
sync
nolock
nommap
cloexec
Note that not all flags are valid with all GNU dbm versions.
- ‘gdbm-setopt!’ handles more options
In addition to ‘cachesize’ and ‘fastmode’, these options are
now also handled:
syncmode
centfree
coalesceblks
mmap
maxmapsize
Note that not all options are valid with all GNU dbm versions.
- new proc: ‘gdbm-getopt’
Although GNU dbm 1.9 and later provide read-access to the
runtime options via the same C func underlying ‘gdbm-setopt!’,
namely ‘gdbm_setopt’, we separate this functionality at the
Scheme level to avoid horrible confusion (most options are both
readable and writable, but there exist some that are write-only
and some that are read-only). See manual.
- tested against Guile 2.0.9
As usual, we lamely keep ‘GUILE_AUTO_COMPILE=0’ in the env.
OTOH, testing is now full flow, i.e., from "sh autogen.sh"
onward, to exercise tools portability, as well.
- bootstrap tools upgraded
- GNU Automake 1.13.4
- Guile-BAUX 20130731.0252.f6841da
tarball, etc, in dir:
http://www.gnuvola.org/software/guile-gdbm/
atom feed:
http://www.gnuvola.org/NEWS.atom
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2013-08-12 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 18:50 Thien-Thi Nguyen [this message]
2013-08-15 15:51 ` Guile-GDBM 1.1.0 available Ludovic Courtès
2013-08-15 18:37 ` dsmich
2013-08-15 20:53 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878v06hhfs.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).