Patrick Ohly wrote:
My conclusion is that a simple check is useful for automatic migration
(which should never cause harm) and not needed for --migrate (which
needs a warning in the documentation).
Automatic migration should be limited to the D-Bus server and thus GUI
users. Command line users can use the --migrate option. Agreed?
Sounds good.
Speaking of documentation, this needs to be overhauled to cover the new
semantic of the "server" name. It's no longer necessarily a server and
may contain a context. I suggest to replace it with "config name" or
simply "config", with an explanation what that means.
I was about to suggest the same thing.
Should we do the same in our source code? Some code passes around a
"server" string, but in reality it is now also a "config". This will be
a massive patch based on lots of automated search/replace. Advantage:
conceptually clean code. Disadvantage: high code churn. Thoughts?
Heh, sounds familiar. A word of warning to anyone looking at the gtk-ui
code: I have a similar situation, but with several terms: "server",
"config", "service" and "session" terms are sometimes used in dubious
contexts because the api changes have made old terms bad choices.
- Jussi
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
