Location of configuration files

[eliandoran]

Hi, @fabiobento512 .

I'm working on packaging this application for Nix (a package manager with reproducibility in mind, for Linux and macOS).

One of the interesting things I saw with this application is the way it treats its configuration file. More specifically, I see that on Linux it uses the current working directory as the location for the configuration. On a Mac, the path is the same as the .app directory it's running from.

Nix, since it's supposed to be reproducible prefers immutable directories and as such it will fail when run on a Mac.

I was wondering if there was a specific decision to using the current directory as the configuration directory instead of the more common ~/.config.

I'd like to know your thoughts on this.

Also it seems that the link from the error message on macOS (https://github.com/fabiobento512/FRequest/issues/5) is no longer there. I think the issue got deleted.

[fabiobento512]

I was wondering if there was a specific decision to using the current directory as the configuration directory instead of the more common ~/.config.

Well one of the reasons is that I wanted it to behave the same on all the operating systems (having the plus of being a portable app), other is that I was unfamiliar with Linux (though not anymore since it's now my main operating system).

In fact I have been thinking in switching it from an app image to a flatpak, not sure how feasible is that, in a way it would break the "portable" aspect of it (like keeping it in a usb stick). Though I would need to find time to work again in this project.

Also it seems that the link from the error message on macOS (https://github.com/fabiobento512/FRequest/issues/5) is no longer there. I think the issue got deleted.

Oh that's unfortunate. I guess the owner of the issue deleted it... Interestingly it's still available in wayback machine: https://web.archive.org/web/20200910210846/https://github.com/fabiobento512/FRequest/issues/5.

To be honest I have been planning in removing macOS support for future releases... In the sense that I don't own a physical mac to test it and apparently using a virtual machine is illegal, or at least it breaks apple's eula.