On 27 September 2015 at 22:51, Sune Vuorela <nos...@vuorela.dk> wrote: > On 2015-09-27, Boudhayan Gupta <bgu...@kde.org> wrote: >> What I propose is that all libraries which want to manage their own >> release cycles and their own namespaces, be moved to Extragear Libs >> and release from there. All the libraries which can stick to the >> Applications release-unit, move to Support or a new module and be >> released with them. > > What happens if an Applications application uses an extragear lib? or an > extragear application uses an application lib? > > Yes. this will happen. > > And then you have a abi/api unstable library out of sync with the > application it uses. And that's highly annoying. > > Seen before with e.g. Digikam/Gwenview/KPhotoAlbum and > libkipi/libkexiv2/...
"Seen before" is no reason to not move forward if we can actually fix this. As I said, Extragear library developers will *have* to provide API/ABI guarantees. > I don't see why we need a extra organizational level to house something > we should try to avoid to have in the fist place. > > Let's get all good libraries made frameworks. That's the ideal scenario, but isn't becoming a framework... hard? Cheers, Boudhayan _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
