wms-import utilitites to allow connect file as parameter

[abeccati]

applications/rasgeo/wms-import/utilities should allow connect file to be specified on command line to allow call with non default connection parameters.

change default expected location (asked by Peter) from user's home to RMANHOME/etc (or /etc), anyways to the default rasdaman installation config dir.

Todo:

• List utils to be updated

Done:

• init_wms

[abeccati]

connect file as parameter to init script

[abeccati]

Patch attached (and submitted 2013-08-30 11:34:15) for the init_wms script; same should be done for all other wms import utilities to close this ticket.
(Enable-init_wms-with-connect-file-parameter.patch)

[Dimitar Misev]

Should it be closed, the patch was applied?

[abeccati]

Let it open, we have to check that all the tools there use the same approach. And also change default expected location (asked by Peter) from user's home to RMANHOME/etc (or /etc), anyways to the default rasdaman installation config dir.
I've updated description accordingly

[Dimitar Misev]

Default expected location of what?

[abeccati]

Default expected location of the connect file. If it is not given as parameter on command line.

[Dimitar Misev]

$RMANHOME/etc does not make sense, it's place for the server's configuration, not the user client tools. User configs should go in $HOME/.rasdaman or so.

[abeccati]

Dimitar, I agree but I have no strong preference here and having a system-level default (customizable by the user) is not that bad: it allows running client tools on the local server from any user with no customization at all.

[abeccati]

Adding also Piero and Alex H so that default config can be changed also in rasimport. This should be shifted as development since there is not much need to maintain it in 8.X unless we get specific requests for it.

[Peter Baumann]

is this still relevant, or can we close it?

[Peter Baumann]

looking at this again, I do like the idea that parameters are visible, and not in some (potentially even hidden) config file - we had issues with that in the past.