Lars Henriksen wrote:
I made the fix after reading the documentation (Keeping Track,
section 4.2) that explicitly excludes your setup:
For a database that is located across a network, but which should be
accessible from this host, the entry for the database should look like
this:
DATABASE NAME:SHORT DESCRIPTION OF DATABASE::HOSTNAME:PORT
The first two fields are the same as for local databases, the third
field is empty (notice the two adjacent `:' symbols, indicating an
empty field), the fourth field is the hostname of the remote GNATS
server, and the fifth field is the port number that the remote GNATS is
running on.
Now, this may be all wrong (and no, I haven't checked the code), but
I agree that the 'fix' to mkdb is according to the documentation, but
I would encourage you to reconsider the documented behaviour.
Supporting two modes is a duplication of effort that gives rise to a
number of the 'arch enemies' of good software engineering....inconsistency,
ambiguity and unnecessary complexity. And in this case, I hold that
it's totally unnecessary.