On Mon, 2008-03-17 at 13:31 +0930, Iain Buchanan wrote:
> Hi,
>
> just looking through the sync-engine code to tweak the gentoo package,
> and I came across this in config.py:
>
> # check if we have a config
>
> self.config_dir = os.path.join(os.path.expanduser("~"), ".synce")
> self.config_path = os.path.join(self.config_dir, "config.xml")
>
> if not os.path.exists(self.config_path):
> if not os.path.isdir(self.config_dir):
> os.mkdir(self.config_dir)
> oldconf = os.path.join(self.sepath,"config/config.xml")
> shutil.copy(oldconf, self.config_path)
>
> so if config.xml doesn't exist in ~/.synce it is copied from
> "self.sepath". The only problem is self.sepath is set to
> "/usr/lib/python2.5/site-packages" a few lines earlier, so the default
> config.xml would have to be installed into
> "/usr/lib/python2.5/site-packages/config/config.xml"
>
> Is that right? I couldn't find any other reference to config.xml.
Just an addendum to my previous message - this is actually correct in
what it is doing. The sync-engine root is one level below
'SyncEngine' (check the tree out from SVN to see what I mean). I can
only assume that the package manager is installing the entire
sync-engine tree to /usr/lib/python2.5/site-packages. If this is the
case, the sync-engine root is the same
as /usr/lib/python2.5/site-packages and the above behaviour is to be
expected.
If packagers need the directory structure of sync-engine changing to
make life easier, please let me know. I avoid getting involved in
packaging so I am not sure where the problems are.
John.
-------------------------------------------------------------------------
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
