summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/doc-docbook/spec.xfpt10
-rw-r--r--doc/doc-txt/dbm.discuss.txt3
2 files changed, 9 insertions, 4 deletions
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 6acdc1a32..6c0ac922d 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -1811,9 +1811,13 @@ the traditional &'ndbm'& interface.
.next
To complicate things further, there are several very different versions of the
Berkeley DB package. Version 1.85 was stable for a very long time, releases
-2.&'x'& and 3.&'x'& were current for a while, but the latest versions when Exim last revamped support were numbered 4.&'x'&.
-Maintenance of some of the earlier releases has ceased. All versions of
-Berkeley DB could be obtained from
+2.&'x'& and 3.&'x'& were current for a while,
+.new
+but the latest versions when Exim last revamped support were numbered 5.&'x'&.
+Maintenance of some of the earlier releases has ceased,
+and Exim no longer supports versions before 3.&'x'&.
+.wen
+All versions of Berkeley DB could be obtained from
&url(http://www.sleepycat.com/), which is now a redirect to their new owner's
page with far newer versions listed.
It is probably wise to plan to move your storage configurations away from
diff --git a/doc/doc-txt/dbm.discuss.txt b/doc/doc-txt/dbm.discuss.txt
index 7df044e82..50f068713 100644
--- a/doc/doc-txt/dbm.discuss.txt
+++ b/doc/doc-txt/dbm.discuss.txt
@@ -41,7 +41,8 @@ some time, and various releases 2.x began to appear towards the end of 1997. In
November 1999, version 3.0 was released, and the ending of support for 2.7.7,
the last 2.x release, was announced for November 2000. (Support for 1.85 has
already ceased.) There were further 3.x releases, but by the end of 2001, the
-current release was 4.0.14.
+current release was 4.0.14. In 2022 it was 5.3.28 on Linux (the then-owner
+has developed it further but Exim does not support anything after 5.x).
There are major differences in implementation and interface between the DB 1.x
and 2.x/3.x/4.x releases, and they are best considered as two independent dbm