Am Montag 31 Mai 2010, 10:05:57 schrieb Rangeen Basu:
Hi,
After moving around the files I need advice. The GNUmed server "package" was
really not designed for distributed files. Since it basically works like
expand the tarball, bootstrap (once), delete all files I wonder if what is the
best way to proceed.
So far it needs three patches to the source code to get it going. However it
still fails to find the needed sql files.
Where are those supposed to live ?
I really would like to raise the question if it is possible to just put all
this in /usr/lib/gnumed-server
Here are the reasons:
the python files which are expected in lib/site-packages are not really
packages. No other program will ever import them. The way it is written now
they will collide with the client files which live in site-packates already.
the *.conf files are not really config files as they are really never changed.
They are used once and noone ever changes them. We could call them *.data
instead of conf if that makes it more clear.
The place for the sql files is not clear.
We have had this discussion with the Debian team before and they have followed
our argument that since this is one-time-use only it is ok to put these in
/usr/lib
The client part is a totally seperate beast and is in the format you would
like to see already.
Please let me know what you think,
Best regards,
Sebastian