Hi, On Mon, Apr 16, 2007 at 12:58:04PM +0200, Marcus Better wrote: > > Is there a reason not to just upgrade the existing packages? Are the > > libraries ABI incompatible? > > It's not clear to me, but they changed the API by moving the header file > opensync/opensync_xml.h, according to Michael, so we need a new -dev package > name or the existing packages will FTBFS (unless we transition all of them to > the new version, which could make sense).
We could also roll-back that rather gratuitious change for 0.22 (modifying most/all plugins) and keep on with the current library name (thoroughly testing things), as the binary-compatibility is said to be there. Another possiblity would be to ship a copy of the new header file at the old location. We'll have to rev the library for 0.30 anyway, I hope upstream will adopt some library versioning for this, but the more active upstream guys seem to be aware of this issue. (according to some OpenSUSE guy I talked to at FOSDEM, 0.30 is due before the next OpenSUSE release I think - before around mid-summer I guess). There's also the issue with the changed user-database format in $HOME/.opensync; I'm not sure how to handle this on upgrade (except for a cop-out NEWS.Debian or debconf notice), as we wouldn't know which front-end the user prefers. In any case, I don't think we should rush new opensync uploads, or we might hit some upgrade-path issues (or rather, get more of them) Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
