FS#1971 - db 4.3 not backwards compatible with 4.2
Attached to Project:
Arch Linux
Opened by Jan de Groot (JGC) - Monday, 03 January 2005, 18:02 GMT
Last edited by Tobias Kieslich (tobias) - Tuesday, 22 February 2005, 23:25 GMT
Opened by Jan de Groot (JGC) - Monday, 03 January 2005, 18:02 GMT
Last edited by Tobias Kieslich (tobias) - Tuesday, 22 February 2005, 23:25 GMT
|
Details
From the PKGBUILD:
# for backwards compatibility ln -sf libdb-4.3.so $startdir/pkg/usr/lib/libdb-4.2.so ln -sf libdb_cxx-4.3.so $startdir/pkg/usr/lib/libdb_cxx-4.2.so Too bad there is no backwards compatibility at all: besides the DB format, also the DB API has changed for a big part. This gives even more problems than leaving the symlinks away. I think it's best to make a todo list for db like we did with python 2.4 and have a db version without symlinks in testing. I don't even think db 4.3 should have moved into current at all in this stage. |
This task depends upon
Those two I can confirm now:
- bogofilter (has its own 0.93.x tree with transaction support)
- courier-family (-imap, -authlib, -mta)
- apache
- heimdal
Other distros solve this by using db4.2 and db4.3 as package names and having headerfiles installed in /usr/include/db4.2 and /usr/include/db4.3
http://www.archlinux.org/devel/todo.php?op=view&id=2
Passing this bug to the next guy on the list. (Hi dorphell! :)
courierstuff is in testing the courier-imap-(x)sql and courier-imap-ldap
will disappear.