Comment 2 for bug 195397

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:

If $HOME/.bazaar exists, let users know that this is now deprecated,
and ask if they would like to migrate to the new config scheme now, or
do so with a command later. Warn them that if they have any other
scripts or programs that use the old .bazaar config, it may break.

If it doesn't exist, use the new scheme. If both exist, use the new
scheme, but warn that an old scheme exists, explaining the transition
so that users now where to find the new settings and user data.

Of course this sounds a lot easier said than done, and I'm writing
this from the perspective of a user who wants to be rid of the upgrade
annoyance he's met with every 6 months.

move all configs / user data to the new $XDG_CONFIG_HOME and
$XDG_DATA_HOME, without separating out details of files yet, so that
each file can be simlinked in the old location.

Perhaps it would be a good idea to first come up with a plan for
transitioning as other projects take on the specification too.

Regards,
Tim

On Mon, Feb 25, 2008 at 6:05 PM, James Westby <email address hidden> wrote:
> Hi,
>
> I think it's a good idea for us to do this, but we need
> to come up with a transition plan.
>
> I guess this is a very common situation to be in, there isn't
> by any chance any support for doing this somewhere is there?
>
> Thanks,
>
> James
>
>
> ** Changed in: bzr
> Importance: Undecided => Wishlist
> Status: New => Triaged
>
>
>
> --
> Bazaar does not follow the Freedesktop XDG Base Directory Specification
> https://bugs.launchpad.net/bugs/195397
> You received this bug notification because you are a direct subscriber
> of the bug.
>