[Dbconfig-common-devel] A few questions about dbconfig-common

[Jes Andersen]

> perhaps you could post your source package somewhere?  there's always the
> possibility that there's a user error or documentation error, as well as
> unintended bug...
At the moment the legal status is unknown but I'm working on getting
as much of the framework as possible licensed under LGPL, but the
company isn't used to open source so it will probably take some time.
Speaking of which I just noticed dbconfig-common is GPL, so we can't
even use it, since that would require the program that links to the
library to use GPL =)

> you should also be able to fix a broken install with dpkg-reconfigure
> packagename.  of course i'd prefer if you could be more specific about
> the problems you're having and see if they can be fixed, but no one
> is holding you at gunpoint here.
Of course and I'll be happy to supply them, but it will be after
crunch time. I think a lot of the problems came from the fact that I
tried to run the way we did, which should be very uncommon.
But a simple documentation problem that should be fixed is at
http://people.debian.org/~seanius/policy/examples/dbconfig-common/doc/dbconfig-common-using.html:
"in the postinst, preinst, prerm, and postrm scripts for your package,
you will need to source the libraries which perform most of the work
for you." <-- s/preinst/config/
"sometimes, a particular package may support multiple database types.
this is common with perl or php based web applications, which
frequently use some form of database abstraction layer (pear DB for
php, DBD::MySQL for perl)." <-- s/DBD::MySQL/DBI/