TOPIC:

Hello,
I am packaging xygrib as replacement for zygrib which seems dead for OpenSUSE.
I have a blocking issue, on first use, XyGrib must launched from the location where the chart are and successfully load a grib, in order for the following time to find the chart.
I have noticed that you add an entry appDataDir=/usr/share/XyGrib in the config.ini file.

As this .ini is created by the code at first execution, it does a search from the current dir going down to each sub dir to find a chart.
It then fails silently.
Issue if it find chart in any dir (even a temp one) it will write in the config file. Which is hidden to most user (.config)

PROPOSITION

---

create a default config file which is installed with the code.
By default the search path could be '.', so today behavior remain the default.
Let us, packager, modify this file with what ever is smart.

E.g I have create a dedicated ghssh package for OpenCPN under OpenSUSE, I will remove the gshhs dir from xygrib at packaging and use the default package.
That will reduce the amount of data to download.
From a boat data can be expensive.

Current behaviour is for me a show stopper as after the install it does not work.

Please let me know your thoughts.
Dominig

P.S. You create 3 config files
~/.config/xygrib.ini
~/.config/xyGrib.conf
~/.config/XyGribrc

Not nice at all.
The 2 config files should be 1 have the same (better none) capitalisation. Under Unix that is important.
a .ini is odd in a Linux box.
The rc file should share the same (better none) capitalisation to respect generic pattern.
The mix in capitalisation dispatch the file is various location when doing a list.

Hello,
see my comment opengribs.org/fr/forum/xygrib-support/67...official-release#311

Hi dominig and welcome to the forum,

The logic for finding the static data files is as follows.

1. The application reads the data location from the configuration files and checks to see if the location is valid.

If there is not a definition of the location in the configuration files or if the location is not valid then the application does the following search for the data structure. One the structure is found the configuration files are updated.

2. The OS is asked for the location of WRITEABLE DATALOCATION to which most linux distros respond with ~/.local/share/openGribs/XyGrib.
3. If not found at 2 above the application lists all DATALOCATIONs possible and checks each one. For Ubuntu these are:
3.1. /usr/share/ubuntu/openGribs/XyGrib
3.2. /usr/local/share/openGribs/XyGrib
3.3. /usr/share/opengribs/XyGrib
3.4. /var/lib/snap/desktop/openGribs/XyGrib

4. If the data structure is not found at any of the above then the folder "data" is searched for in the application's installation folder.

I would recommend placing the data structure in user home space i.e. ~/.local/share/openGribs/XyGrib. This is where the Linux installer will place the data files on all distros. The other options shown above will also work.

I hope that this answers your question

David
I have proposed a patch that adds coverage for the case /usr/share/XyGrib
It waiting in a pull request.
github.com/opengribs/XyGrib/pull/163
Dominig