[Dbconfig-common-devel] Questions about upgrading

[sean finney]

hey karsten,

On Sun, Jul 09, 2006 at 01:27:40PM +0200, Karsten Hilbert wrote:
> After all, if a package supports multiple database instances
> in, say, different database engines and/or even in different
> versions then it should really provide:
> 
>  gnumed-server-pgsql-0.1.deb
>  gnumed-server-mysql-0.1.deb
>  gnumed-server-pgsql-0.2.deb

in some, but not all cases.  a php-based webapp, for example, might
likely only have one package, and then depend on php4-mysql | php4-pgsql,
for example.   but these are actually the "easy" apps to multi-instance,
because usually they don't involve more than generating a few
differently named/valued configuration files for each instance.

the tricky apps are the ones that are more tied into the underlying
system, such as apps that need a seperate running daemon to talk to the db
or a seperate user per instance, or something along those lines.  at some
point this becomes nearly impossible to accomplish by dbconfig-common,
but i think it's possible to get most of the way there, leaving the
packager to work out the final specifics.

if you're interested in hearing about what's going on with the
multi-instance work that i'm doing, i can do a brain dump onto
the list when i start doing the commits for it, but that probably
won't be until after etch as i'd like to get/keep things stable 
for etch.  or maybe not, who knows :)


	sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20060710/f801f9cc/attachment.pgp