On Friday, December 27, 2013 17:31:39 Sandro Knauß wrote: > Till now all versions of ocsync has the same libary version (0.2.1) and the > same SONAME (0) version. For all applications that use ocsync this is > awfull, 'cause you break the API and ABI in nearly every version. So please > bump the SONAME if you break the ABI (more informations see [1]). > > Actually the only application I know is pyOwncloud[2], where we have now > the problem, that we get all differnet versions of ocsync [3,4]. > > Ok a more stable API would also be very nice. But I know ocsync is still > under heavy development.
I second that this is necessary. Easiest would probably be to tie the SONAME to version of mirall, so you release a new version -> SONAME changes. That way you can't forget to do it prior to a release, and it's only painful for those using mirall from git (which is fine with me). Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 _______________________________________________ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud