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

[sean finney]

hi andreas,

On Thu, Dec 16, 2004 at 08:56:32AM +0100, Andreas Tille wrote:
> To make something clear: dbconfig-common does a lot of interesting stuff
> for generalizing the installation of any database containing package and
> thus is a great help for Debian developers.  What it does not is to
> organize a sequence in which SQL files are imported into the database.
> It just relays on either a simple flat SQL file or a bootstrap script
> (as it is provided for instance by GnuMed).  (Sean, please correct me
> if I underestimate your work.)

this is correct.  like i said in an email last night though, i'm not against
providing a means to run multiple scripts/sql files if there were enough need.

> >OK, that's good. You're still using debconf to ask these config questions 
> >though?
> Yes.  This would leave the question if it might make sense to port debconf
> to other systems, but I doubt that this is worth the effort only to install
> GnuMed.

well, the package could be further generalized to only use debconf on
systems that have it, and default to using readline or something of the
like for other systems... though this is slightly outside of the scope
of what i'm doing currently.  

> >>if you want to use a bootstrapping script due to its cross distro
> >>nature, 
> >Not really, my main aim is to move maintenance of bootstrapping scripts 
> >from us to you ;-)
> :)
> You should care for Debian world domination first but I doubt that making
> GnuMed dependant from Debian is the right way to approach this. ;-)

in all honesty, i'd agree.  i think it is true however that debian does
often greatly enhance the usability of the software it provides.

On Thu, Dec 16, 2004 at 09:02:17AM +0100, Andreas Tille wrote:
> >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.

that would be you guys, right?  :)  seriously though, since this
behaviour wouldn't interfere with packages with simpler needs
(packages can't have a '_' in their name, anyway) i wouldn't be
against providing a feature like this if it makes life substantially
easier for someone.


        sean

--

signature.asc
Description: Digital signature