Bug#564334: cameleon: Config files not preserved when updating.
Le Tue, 19 Jan 2010 09:09:13 +0100,
David MENTRE <email@example.com> a écrit :
> 2010/1/19 Guillaume Yziquel <firstname.lastname@example.org>:
> > Mehdi Dogguy a écrit :
> >> IMHO, It's not even an issue. We changed the used library and its
> >> configuration directory changed as well since it matches the
> >> library's name.
> > You upgrade a package. You lose your configuration. This is not an
> > issue.
> > ?
> I would be inclined to agree with Guillaume and say in such case that
> this is an error not to keep configuration from one version to the
> other of the same software.
> On this other side, as an application developer, doing and maintaining
> such upgrade path can be complicated and should be balanced with the
> impact of re-doing the configuration for the user. I don't know
> Cameleon but I assume re-configuring the application is not such a big
> task. Moreover, in this particular case, the non-upgrade issue should
> appear only once. So closing this bug seems to me quite reasonable.
> Maybe adding a short note in README.Debian could be useful.
Indeed, there is only four or five parameters to set up in a dialog
There is a big change between sourceview and sourceview2: gtksourceview
defines styles for each element of each language supported for syntax
highlighting, but gtksourceview2 now supports only a global style and
and relies on a mapping from each language's syntax elements to some
kind of categories (keyword, comment, ...). The global style defines
colors, etc. for these categories. So the previous configuration is not
really usable, except for common attributes like the font, its size, ...
This is why I chose to use a different configuration directory.