diff options
author | Sergey Poznyakoff <gray@gnu.org> | 2018-05-19 22:59:10 +0300 |
---|---|---|
committer | Sergey Poznyakoff <gray@gnu.org> | 2018-05-19 22:59:10 +0300 |
commit | 008b71a4d58ad33cf5a41e2aa55b9393e8420531 (patch) | |
tree | 2923a1840dcd1c2108bfe13b6817bfd8ddcc19d2 /NOTE-WARNING | |
parent | 0f0c3dba3f676bf7a163586855f07ef427da3b4a (diff) | |
download | gdbm-008b71a4d58ad33cf5a41e2aa55b9393e8420531.tar.gz gdbm-008b71a4d58ad33cf5a41e2aa55b9393e8420531.tar.bz2 |
Remove gdbm-1.8.3 compatibility layer
* configure.ac: Remove gdbm-1.8.3 compatibility layer.
Version 1.14.90
* Makefile.am (ACLOCAL_AMFLAGS): Remove deprecated variable.
(MAYBE_EXPORT): Remove variable and conditional.
* NEWS: Update.
* NOTE-WARNING: Update.
* README: Update.
* doc/gdbm.texi: Update.
* export/.gitignore: Remove.
* export/Makefile.am: Remove.
* export/export.c: Remove.
Diffstat (limited to 'NOTE-WARNING')
-rw-r--r-- | NOTE-WARNING | 35 |
1 files changed, 12 insertions, 23 deletions
diff --git a/NOTE-WARNING b/NOTE-WARNING index 6b1c197..3f21c13 100644 --- a/NOTE-WARNING +++ b/NOTE-WARNING @@ -7,28 +7,17 @@ system architectures, or potentially even different compilers. Differences in byte order, the size of file offsets, and even structure packing make gdbm files non-portable. -Gdbm version 1.9 includes `large file' support, enabling it on operating -systems where it is not the default. `Large file' support is essentially -when a system uses 64bit file offsets. Gdbm has, of course, supported `large -files' on systems where it was the default for a very long time. - -On some systems, such as Solaris, this functionality is not enabled by -default. Gdbm will now enable it. THIS MEANS THAT GDBM 1.9 MAY NOT BE -ABLE TO ACCESS DATABASES CREATED BY PREVIOUS VERIONS ON THE SAME SYSTEM. - -Running the `configure' script with the `--disable-largefile' flag should -produce a backwards-compatible build on such a system. However, for maximum -compatibility, and increased functionality, you may want to have your -application produce a portable copy of your database with the 1.8.3 version -of the library, and then load it back into version 1.9. - -Gdbm 1.9 contains a utility designed to help you produce such a portable -copy: gdbmexport. To build it, configure the package with the ---enable-gdbm-export option. For the information on how to use this -utility, refer to the documentation, chapter 17 "Export a database into -a portable format." (run `info gdbm gdbmexport' to access it, once -gdbm 1.9 has been installed, or `info -f doc/gdbm.info gdbmexport' to -access the shipped info file). - +Therefore, if you intend to send your database to somebody over the wire, +please dump it into a portable format using gdbm_dump and send the resulting +file instead. The receiving party will be able to recreate the database from +the dump using the gdbm_load command. + +Please refer to the documentation, chapters 22 and 23, for a detailed +discussion of these two tools. Run `info gdbm gdbm_dump', if gdbm is +already installed on your system, or `info -f doc/gdbm.info gdbm_dump' +to read the docs from the source tree. + +The documentation is also available online at +http://www.gnu.org.ua/software/gdbm/manual. |