OpenPKG CVS Repository http://cvs.openpkg.org/ ____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer Root: /e/openpkg/cvs Email: [EMAIL PROTECTED] Module: openpkg-re Date: 30-Jan-2004 10:26:03 Branch: HEAD Handle: 2004013009260300 Modified files: openpkg-re upgrade.txt Log: remember ndbm issue leading to possible file format incompatiblity Summary: Revision Changes Path 1.20 +11 -1 openpkg-re/upgrade.txt ____________________________________________________________________________ patch -p0 <<'@@ .' Index: openpkg-re/upgrade.txt ============================================================================ $ cvs diff -u -r1.19 -r1.20 upgrade.txt --- openpkg-re/upgrade.txt 20 Jan 2004 23:59:45 -0000 1.19 +++ openpkg-re/upgrade.txt 30 Jan 2004 09:26:03 -0000 1.20 @@ -2,7 +2,7 @@ General Notes ============= - o $Revision: 1.19 $. The most recent update of this file can be + o $Revision: 1.20 $. The most recent update of this file can be downloaded from http://cvs.openpkg.org/openpkg-re/upgrade.txt o This file upgrade.txt file talks about tweaks and quirks when @@ -95,6 +95,16 @@ with_mod_php_unixodbc with_mod_php_odbc with_openssl with_ssl with_tls with_ssl + + o ndbm + + Vendors begin to remove ndbm from their distributions. Debian 3.1 + (sarge) is known to be one of them. Go the OpenPKG independence + way and use own ndbm compatiblity provided by gdbm. This might + break existing installations due to gdbm_ndbm not being file format + compatible to vendor ndbm. Existing ndbm files must be rebuild or + applications must explicitly use vendor ndbm (if available) by being + build with no gdbm_ndbm. See http://cvs.openpkg.org/chngview?cn=14523 Upgrade from OpenPKG 1.2 to OpenPKG 1.3 ======================================= @@ . ______________________________________________________________________ The OpenPKG Project www.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]