Kalle Kivimaa wrote:
If a webapp wants to use a DB, it is up to the maintainer of that webapp package to decide which DB's s/he is going to support.
Why don't you let the administrator decide upon the database? After all, that's what the SQL standard and the JDBC driver/JNDI datasource architectures are designed for.
I'd guess that I would simply link all those JDBC libraries which are in main (actually, I probably need to do this when JSPWiki 2.4 comes out), but some other maintainers might take a different approach.
Does this mean that if I'm going to install JSPWiki 2.4, that package depends on drivers of all databases in main, and thus I have to install all those drivers? I'm afraid I'm not very happy with this solution, because I'd like to limit to just one database system. Why would I want drivers for dozends of DBs on my system if I'm only going to use Postgres?
Also, what approach are you going to take with tomcat5-admin? The admin uses Realms for authentication if this hasn't changed lately, so the database driver cannot be copied/linked to WEB-INF/lib rather than common/lib.
_______________________________________________ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
