On Thu, May 15, 2003 at 05:31:23PM +0100, Richard Boulton wrote:
> On Thu, 2003-05-15 at 14:34, Thomas Leonard wrote:
> > Users aren't supposed to mess with the MIME
> > stuff, although MIME-Editor should probably store any changes they do make
> > in Choices, indeed.
> Surely not - I would have thought that any changes that a user makes
> that overshadow things in /usr/share/ and /usr/local/share/ are changes
> to data, and hence should go in $XDG_DATA_HOME. Just because the user
> changes it doesn't mean it's a config thing, does it? (especially when
> the user isn't normally expected to change it).
It depends whether we expect it to be changed. During the transition
period it will probably need to be. I was thinking of symlinking from the
data directory into Choices.
The point being, you want to back up configuration, but not
application-installed data (eg, the main MIME database is 700K).
> On a slightly different issue, I've just read the spec you referred to,
> and while ROX-Lib2 appears to be complying with it regarding
> $XDG_DATA_HOME and $XDG_DATA_DIRS, the spec also describes
> $XDG_CONFIG_HOME and $XDG_CONFIG_DIRS. These latter two seem to me to
> be describing the paths which Choices should be written to and read
> from. Should rox as a whole be moving to use these instead of the
> $CHOICESPATH environment variable?
Yes, but not yet ;-) The spec is still a draft, and there's no major
hurry (and you can always set CHOICESPATH to use exactly the same
> I also notice that MIME-Editor is not using the $XDG_DATA_* variables,
> anyway. (unless I'm misreading the code)
Correct. The MIME spec only just switched to using the base dir spec.
ROX-Lib needs a basedir.py module which handles it, and then MIME-Editor
can use that.
Thomas Leonard http://rox.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1