|
From: Chris F. <cd...@fo...> - 2009-09-26 08:24:52
|
On Sat, Sep 26, 2009 at 09:26:43AM +0200, Daniel Gollub wrote: > > - pkg-config: > > > > 0.22: opensync-1.0.pc > > 0.40: libopensync.pc (should be libopensync1.pc, but no biggie) > > Need to check why we took libopensync.pc not libopensync1.pc .... Let me know if you find out. I can patch this if needed. > > If this were implemented, it would be possible to write applications > > that support both libraries at runtime, which I'm working on right now. > > Hmm interesting ... do you really think it's worth to stay with 0.22 for long? Well, depending on when 0.40 comes out, there will probably still be 6 months before it gets included in fast-moving distros such as Ubuntu and Fedora. And users often upgrade sometime after that. And some users may need the 0.22 plugin even while using 0.40 for other things. Just a guess. Maybe my fears are for nothing, but I certainly plan on having both installed just to support users, and it would be a pain if I kept clobbering my own test configs. :-) > And i'm also not quite sure if it's really worth to put so much effort in > supporting several APIs - at least so early ... Well, 0.22 is already there... if 0.22 and 0.40 don't conflict then 0.22 is just there as a happy backup, maybe even for OSyncUpdater. I wouldn't look at it as unnecessary API support... 0.22 won't go away too fast, I think. > But if someone wants to take care about this i'm not going to stop her/him ... > At least i'm going to concentrate on a "simple" update-path for now ... So just to be clear, if I come up with a patch for OSyncUpdater, I can change 0.40's default config directory from ~/.opensync to ~/.libopensync1 ? Thanks, - Chris |