[Gnumed-devel] Re: using dbconfig-common in gnumed

[Andreas Tille]

On Thu, 16 Dec 2004, sean finney wrote:

> okay.  well the first idea that comes to mind is to concatenate them
> into one larger file.
Alternatively you might keep the number sorted SQL files in your CVS
but concat all these files in the released tarball.  This definitely
would ensure that the bootstraping works on the user side with allways
the same SQL file (which might be verified by a MD5sum even) and
avoids that user try dirty tricks with changing the sequence of
SQL files in the config file.

> currently, it looks for files matching:
>
> /usr/share/dbconfig-common/data/$package/install/$dbtype
> /usr/share/dbconfig-common/scripts/$package/install/$dbtype
>
> i suppose that could be extended to
>
> /usr/share/dbconfig-common/data/$package/install/$dbtype
> /usr/share/dbconfig-common/data/$package/install/$dbtype_$arbitrarystring
> /usr/share/dbconfig-common/scripts/$package/install/$dbtype
> /usr/share/dbconfig-common/scripts/$package/install/$dbtype_$arbitrarystring
>
> and be guaranteably sorted via... sort or something.
This is IMHO a good idea but we should spread this over people who
write database applications in general.

Kind regards

         Andreas.

--
http://fam-tille.de