-
Notifications
You must be signed in to change notification settings - Fork 334
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
Fix paths #148
base: master
Are you sure you want to change the base?
Fix paths #148
Conversation
ExamplesXDG level 0RHEL
Freedesktop
XDG level 1RHEL
Freedesktop
XDG level 2RHEL
Freedesktop
XDG level 3RHEL
Freedesktop
|
I wonder if it would be better to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This XDG levels thing is in my opinion unnecessary complex.
Some levels make no sense. I can't see a situation where someone would compile with --enable-xdg-dirs=1
or --enable-xdg-dirs=2
:
- at level 1, what should go to
$XDG_DATA_HOME
would go to$XDG_CONFIG_HOME
. This is even worst than using the old$HOME/.aegisub
. - level 2 is useless: if someone wants cache to
/tmp
they just have to set$XDG_DATA_CACHE
accordingly.
Can't we just eliminate intermediate levels, and actually fully comply to the specification with an additional check for legacy paths at runtime for backward compatibility?
Fix paths
Allow to use a custom path for dictionaries
You can use the
--with-dict-dir=PATH
option to specify the path for dictionaries, e.g./usr/share/hunspell
,/usr/share/myspell
,/app/share/hunspell
,/usr/local/share/hunspell
,/opt/share/hunspell
, etc.Respect the XDG Base Directory Specification
Add 3 options:
--disable-xdg-dirs
--enable-xdg-dirs
--enable-xdg-dirs=LEVEL
Possible levels:
XDG_CONFIG_HOME
XDG_DATA_HOME
XDG_CACHE_HOME
Print platform specific paths
Print values of the platform specific paths:
?user
?local
?data
?dictionary
?temp