Skip to content

Store config data in $XDG_DATA_HOME/megaCmd instead of ~/.megaCmd#797

Open
jirutka wants to merge 1 commit into
meganz:masterfrom
jirutka:xdg-data-home
Open

Store config data in $XDG_DATA_HOME/megaCmd instead of ~/.megaCmd#797
jirutka wants to merge 1 commit into
meganz:masterfrom
jirutka:xdg-data-home

Conversation

@jirutka

@jirutka jirutka commented Apr 2, 2023

Copy link
Copy Markdown

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.

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
@ChrisLane

ChrisLane commented Jul 1, 2024

Copy link
Copy Markdown

@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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants