On Mon, 2008-02-25 at 20:44 +0000, Tim Kersten wrote:
> I don't know of any support for transitioning, and I can well imagine
> it not being a painless process. Perhaps the most sane default would
> be something along the following:
Thanks for your comments.
My personal preference would be to get support for reading from these
locations in soon. Then in a couple of releases start a transition
proper by changing the docs to point to the new location, and using
them when autocreating the files. Then after a while we can start
warning the user if they are using the old location, then finally
stop supporting them in v2 or similar.
However, I am not sure whether we are ready for the .config/ .local/
split. Most of what is in there is configuration I think, with
the exception of plugins, which I guess are data.
On Mon, 2008-02-25 at 20:44 +0000, Tim Kersten wrote:
> I don't know of any support for transitioning, and I can well imagine
> it not being a painless process. Perhaps the most sane default would
> be something along the following:
Thanks for your comments.
My personal preference would be to get support for reading from these
locations in soon. Then in a couple of releases start a transition
proper by changing the docs to point to the new location, and using
them when autocreating the files. Then after a while we can start
warning the user if they are using the old location, then finally
stop supporting them in v2 or similar.
However, I am not sure whether we are ready for the .config/ .local/
split. Most of what is in there is configuration I think, with
the exception of plugins, which I guess are data.
This would be a long task it seems.
Thanks,
James