On Tue, 2008-05-20 at 12:38 +0100, Dr J A Gow wrote: > I would be happy to take the approach of scanning /etc, then ~/.synce, > and if unset use the app defaults. > > Alternatively, packagers could put the template file in somewhere > sensible, such as /usr/share/synce/examples or similar, where it could > be found by users who want to customize their configuration.
I think it's actually fine to install a copy (as discussed earlier, with all values commented out) to ~/.synce/config.xml when first running synce - as we all understand it's purely to hint to the user that they can indeed use a file in that location to change sync-engine's configuration. The usual behaviour is that an application creates the per-user config file when you first make a change to the configuration within the app itself, but this doesn't apply to sync-engine, as you can't change any of the settings in the config file from 'within' the app. So given that, having it created on first run is sensible enough, and probably better than expecting people to learn from documentation, or guess, that they can copy the system-wide file there and edit it. The thing I was really objecting to initially in the this thread was never the creation of the file per se, but the fact that it had values explicitly set by default. BTW, for what it's worth, I currently patch sync-engine in Mandriva to install the template config file to self.sepath,"SyncEngine/config/config.xml" rather than self.path,"config.xml" . -- adamw ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
