|
From: | Jim Busser |
Subject: | Re: [Gnumed-devel] Naming convention (Was: Choice of programming language and project management) |
Date: | Mon, 07 Sep 2009 20:44:08 -0700 |
On 7-Sep-09, at 4:09 PM, Karsten Hilbert wrote:
I believe it is equally valid either way (putting both under /etc/ gnumed/ as well as separating into /etc/gnumed-client/ and /etc/gnumed- server/.Now, what *is* "gnumed-backup.conf" ? Put it under gnumed-server/ or gnumed-client/ ?
Well, while using plain gnumed/ avoids answering the question, it is likewise avoided by doing as follows:
- if it is the server package that is copying gnumed-backup.conf then put it in
/etc/gnumed-server/ and if it is the client package/installer let it put it in /etc/gnumed-client/ what could be simpler than that?If plain gnumed continues to make sense for established packagers then I feel no need to push this but only pointed out the above simplicity as an additional consideration if reasons to reconsider would be renewed.
[Prev in Thread] | Current Thread | [Next in Thread] |