http://bugzilla.moblin.org/show_bug.cgi?id=7808
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2009-11-04 23:55:27 ---
(In reply to comment #1)
* if the config is not suitable for cloning, add a big warning at the
top of
the file to help folk like me know that what they are doing is fraught
Sounds reasonable. A README in the top-level /etc/defaults/syncevolution
directory also would be useful.
* if the config is suitable for cloning, include all the comments
there
It's not.
* /etc is preferable for linux folk. In that case, convention is for
that
config to represent 'base' configuration; i.e. a fallback that is used if more
local config (e.g. in ~/.config/syncevolution) is not found.
The configs in /etc cannot be used for syncs, only to create configs. In that
sense a better location would be /usr/share/syncevolution for the templates
that come with the distribution *plus* the possibility to search for templates
in /etc/defaults/syncevolution.
The intention was that local sys admins can extend the set of server templates
without having to recompile SyncEvolution. Admittedly a rather obscure and rare
use-case, so I wonder whether it is worth bothering about at all.
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.