Hello, 2010/1/19 Guillaume Yziquel <[email protected]>: > 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. Best regards, d. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
