hi all, i'm packaging (again, last maintainer orphaned it in experimental) jabberd2 for debian, but i'd like to rise two questions:
1.- if jabberd 2.x is completely different from jabber 1.x why it is not released has jabberd2-version ? maybe this way could make the difference more clear. 2.- in the revision 180 it was fixed bug #52: Make the database drivers loadable modules. now, plugins should be dynamically loaded, but when i compile with --enable-ldap --enable-db for example, ldd shows those libraries linked. this should not be the case when libs are loaded by dlopen. until now, jabberd has been packaged with different flavours: * ldap-db * mysql * postgresql and so on ... if database drivers are really loadable at runtime, only one flavour would make sense. can anybody explain this behaviour a bit ? regards _______________________________________________ jabberd2 mailing list [email protected] http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
