Re: [Gnumed-devel] Issues with 0.5 detected when trying to package

[Jim Busser]

On 15-Aug-09, at 7:06 AM, Andreas Tille wrote:

issues I want to discuss:

1. gnumed-client.conf.example:

...

[profile public GNUmed database]

host = salaam.homeunix.com

port = 5432

database = gnumed_v10

I understand that if a user were to take the example file and copy it in order to use it as gnumed-client.conf, it would try to connect to the "wrong" database and presumably fail on account of a mismatch (with mismatch defined somewhere other than just the .conf file).

However

1) the file*is* named example

2) the source presumably includes a separate file

gnumed-client.conf

which would be the more essential file in which to have to update the version number, despite that it may have to be done manually.

Suggest that if it is appropriate for gnumed-client.conf and gnumed-client.conf.example to be identical except for their filenames, then it becomes even easier because as part of a release one would need only to update one file and then from it clone the other... even this may already be doable for maintaining sync between the client gnumed.conf and the gnumed server copy of gnumed-client.conf

If .example needs to contain a superset of information that should not be in plain ".conf" then maybe it would be enough in .example to insert a comment line above the "database" line saying:

# database version almost certainly needs updating