On Fri, Jun 11, 2010 at 03:17:18PM +0200, David Engster wrote:
David Engster writes:
I'm trying to understand which problem exactly is solved by this. I
tried to read the "XDG Base Directory Specification" [1] but I admit I
didn't get past "Basics". How is fiddling with XDG_DATA_HOME,
XDG_CONFIG_HOME, XDG_DATA_DIRS, XDG_CONFIG_DIRS and XDG_CACHE_HOME
better than a dotfile or dot-directory in your $HOME?
OK, I've tried the next section.
Can someone explain to me what XDG_DATA_HOME really is for? I know what
the spec says ("directory relative to which user specific data files
should be stored"), but then it doesn't make sense to me that its
default is '~/.local/share'. Since XDG_DATA_DIRS default is
'/usr/share:/usr/local/share', and data in XDG_DATA_HOME overrides
those, it seems they want to mimic the share hierarchy locally? They
somehow want to separate configuration from user data, but then they mix
user data with application data? I don't get it.
Like I said, the spec is verging on batty as is. I still haven't
figured that out myself, and that's after searching the
directories on my computer and seeing what other apps've done.
My best guess on the matter is that .config should be more for
user-editable things, and .local/share for — other local crap, I
guess. Current apps don't really seem to discriminate.
--
Kris Maglione
Advertising may be described as the science of arresting human
intelligence long enough to get money from it.
