Config files are loaded from paths incosistent with debian packaging

[poobarb]

The FCM documentation states that config files (such as keywords.cfg) are located from the following list of paths:

• [$HOME/.fcm in some cases]
• $FCM/etc/fcm/<configfile>
• $HOME/.metomi/fcm/<configfile>

However, the Debian package for FCM (cf. here) installs the confing files to /etc/fcm (a choice which is not unreasonable), whilst it installs FCM itself to /usr/bin/. This leads to the expected config path being /usr/etc/fcm/ rather than /etc/fcm. Hence the config files are ignored.

Could FCM be modified to search the path /etc/fcm as well, leading to the following search order?

• [$HOME/.fcm in some cases]
• $FCM/etc/fcm/<configfile>
• /etc/fcm/<configfile>
• $HOME/.metomi/fcm/<configfile>

[matthewrmshin]

Hi, the Debian package is not actually maintained by us. I think it is maintained by @amckinstry so you may want to check with him as well.

Otherwise, the search location is defined here:
https://github.com/metomi/fcm/blob/master/lib/FCM/Util.pm#L106
So, it should be very easy to add /etc/fcm/ to it.

Note: the $HOME/.fcm location is obsolete.

[amckinstry]

This change will be in Debian version fcm_2017.10.0-3, uploaded to unstable today.

[matthewrmshin]

Hi @poobarb do you want us to make a change or are you happy with the solution provided by @amckinstry ?

[poobarb]

Hi, sorry - just realised I never responded to this...

Thanks for changing the Debian version, that fixed the issue. However, I guess it would still be good to get this fixed upstream too!