> 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.

Update: It's not binary compatible. Here, for instance, is a clear ABI and API 
change:
http://www.opensync.org/changeset/1443#file4

Notice how osync_time_vtime2unix() gets an additional argument. This happened 
between 0.19 and 0.20.

So I guess the libs have to be renamed after all.

What do you want to do, upload 0.22 or wait for 0.30?

Marcus

Attachment: pgpKX9DgQGjjx.pgp
Description: PGP signature

Reply via email to