Store config data in $XDG_DATA_HOME/megaCmd instead of ~/.megaCmd #797
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If `$XDG_DATA_HOME` environment variable is not set, it will fallback to the previous behaviour and use $HOME/.megaCmd. This is a breaking change, so package maintainers and users should be instructed to move `$HOME/.megaCmd` to `$XDG_DATA_HOME/megaCmd`, if they use XDG directories (most desktop distros use them by default). Or you can implement some auto-migration procedure. `$XDG_DATA_HOME` defines the base directory relative to which user-specific data files should be stored [1]. On modern Linux systems, applications should follow XDG directories standard and don't clutter $HOME with dot files and directories. [1]: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html [2]: https://wiki.archlinux.org/title/XDG_Base_Directory
|
@jirutka I am in favour of using XDG directories but I suggest adding backward compatibility by only using your behaviour for new directories and using the old default if the directory already exists. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If
$XDG_DATA_HOMEenvironment variable is not set, it will fallback to the previous behaviour and use $HOME/.megaCmd.This is a breaking change, so package maintainers and users should be instructed to move
$HOME/.megaCmdto$XDG_DATA_HOME/megaCmd, if they use XDG directories (most desktop distros use them by default). Or you can implement some auto-migration procedure.$XDG_DATA_HOMEdefines the base directory relative to which user-specific data files should be stored 1. On modern Linux systems, applications should follow XDG directories standard and don't clutter $HOME with dot files and directories.