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

[sean finney]

hi frédéric,

On Thu, Feb 11, 2010 at 07:44:23PM +0100, PICCA Frédéric-Emmanuel wrote:
> > 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 ?

i think you can still get what you want using the "frontend" functionality
in dbconfig-common.  i wouldn't recommend removing the postrm script
as it also takes care of some other things.  in the frontend mode it
does all the configuration/debconf stuff but never actually talks to the
database.  the install/upgrade support is probably de-activated in the
frontend mode, but since it generates a config file (and you can
also generate another one customized for your needs) you could always
run something yourself in the postinst after calling dbc_go.


	sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20100211/9c56a973/attachment.pgp>