Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Adhering to xdg-base-dir standard #32

Open
mqus opened this issue Mar 15, 2019 · 1 comment · May be fixed by #33
Open

Feature Request: Adhering to xdg-base-dir standard #32

mqus opened this issue Mar 15, 2019 · 1 comment · May be fixed by #33

Comments

@mqus
Copy link

mqus commented Mar 15, 2019

I just found out about your tool and it seems to be just the tool I missed for a while, I have only one gripe with it:
It forces me to put another directory in my already-bloated home directory. Therefore I suggest to make use of the XDG Base Directory Standard (https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html#basics) to locate for the customizepkg directory. For backwards-compatibility we could still look into the old directories, but I would really like it if we have the standard-conforming paths as default in the README.

For example, without setting $XDG_CONFIG_HOME, the files would now be expected to be in ~/.config/customizepkg instead of ~/.customizepkg. For the global configuration, if $XDG_CONFIG_DIRS is unset, use /etc/xdg/customizepkg.d instead of /etc/customizepkg. But to be honest, I think we can let the default for the global directory stay the same and simply use $XDG_CONFIG_DIRS if it's set.

This has the advantage of making a backup of all user configuration files (of all programs using the xdg-standard) simpler than listing all folders in ~ which should be backed up. This also makes it configurable for users who have their own idea of where config files should go.

@mqus mqus changed the title Feature Request: Adhering to xdg Feature Request: Adhering to xdg-base-dir standard Mar 15, 2019
@ava1ar
Copy link
Owner

ava1ar commented Mar 15, 2019

I have no problem with this. May be you want to provide the PR with the feature?

@mqus mqus linked a pull request Apr 9, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants