[Dbconfig-common-devel] RE : package that must not manage a database but can write on it

[PICCA Frédéric-Emmanuel]

> if tango-starter needs database access when it's being isntalled (as opposed
> to when other packages are being installed, i wasn't quite sure how
> to interpret the above), one option is to simply use the config from the
> tango-db package and not have dbconfig-common used in both packages.  of
> course to do this tango-starter would need to depend on tango-db.

> if tango-starter might be installed seperately from tango-db, you could
> use the "frontend" functionality, which is normally designed to be a
> read-only interface (it won't create databases or run sql).  in this
> case you would have to populate the database yourself in your own postinst,
> though you could use the dbconfig config file generated (or make one in
> your own language using dbconfig-generate-include).

this is the second proposition.

tango-stater must be install on each computer of the control system, but the tango-db must
install only once for a network.

so what about removing the purge in the postrm of tango-starter to avoir removing the database ?

>--------
if [ -f /usr/share/dbconfig-common/dpkg/postrm.mysql ]; then
  . /usr/share/dbconfig-common/dpkg/postrm.mysql
  dbc_go tango-starter $@
fi
<---------

thanks

Frederic