[Gnumed-devel] using dbconfig-common in gnumed

[Ian Haywood]

>     - we desperately need to overhaul the bootstrapping experience.
> The Debian guys are doing interesting work
> [http://people.debian.org/~seanius/policy/dbconfig-common.html]
> however using this functionality intersects with about 50% of our
> current bootstrapper. 

I would like to propose this more formally

This is not just a packager's issue, as it would largely replace our own 
Python bootstrapping script. [Of course there would be nothing to stop 
people from still using that script, but it would likely be left 
unmaintained]

Advantages:-
	- relieves maintenance of the bootstrapper and Psql.py, including 
connecting, making databases, etc..
        - debconf, with its various frontends
        - Andreas will probably do this anyway.
        - does upgrading, which we are yet to tackle.

Disadvantages:
	- ties us to Debian, others need to run .sqls manually or use another 
script (which already exists for Cygwin, thanks to Syan)
	- we need to control the order in which .sqls are run, does 
dbconfig-common do this?
	- the scripts gmAuditSchemaGenerator.py, et al., need to use debconf to 
get the connection parameters. (yes there is a python binding), or 
command-line for non-Debian systems, or should we just run them from 
postinst?

we would need 4 packages
        - gnumed-db-core
	- gnumed-db-au & gnumed-db-de, the language extension packs, which 
depend on gnumed-db-core.
        - gnumed-db-test (which depends on *gnumed-db-de*)

Ian

signature.asc
Description: OpenPGP digital signature