|
From: Chris F. <cd...@fo...> - 2009-09-26 03:49:37
|
Hi, I posted about this before, and was pointed to the following ticket: http://opensync.org/ticket/890 It appears that this ticket suggestion was not used. So there is the possibility of configurations conflicting between 0.22 and 0.4x. Fortunately, the following conflicts are resolved: - pkg-config: 0.22: opensync-1.0.pc 0.40: libopensync.pc (should be libopensync1.pc, but no biggie) - include directories: 0.22: /usr/include/opensync-1.0 0.40: /usr/include/libopensync1 - library names: 0.22: libopensync.so.0 and libosengine.so.0 0.40: libopensync.so.1 - plugin directory: 0.22: /usr/lib/opensync/plugins 0.40: /usr/lib/libopensync1/plugins Unfortunately: - HOME config 0.22: ~/.opensync 0.40: ~/.opensync I like the suggestion in #890. At least the 0.40 directory. Even a ~/.libopensync1 directory would be good... actually that's probably best. Since all configuration is supposed to be done through opensync anyway, the actual name of this directory shouldn't matter, and should, in my opinion, get renamed as the API and config formats change. If this were implemented, it would be possible to write applications that support both libraries at runtime, which I'm working on right now. As it is, I'll likely have to use non-standard configdirs for my app, which will separate it from all other opensync apps. This is ok too, I suppose, but not ideal. - Chris |