Sune Vuorela wrote:
> I do think that having things named KF5 that aren't actual frameworks is
> bad for several reasons.
>
> 1) It blurs what's a framework
That's more a political distinction than a technical one. For all practical
purposes, the application using the library doesn't care whether it is a
"Framework" or not.
> 2) We promise ABI and API compatibility for frameworks, but not for
> other things
But it means you will gratuitously break both source (!) and binary
compatibility for all users of the library when the library actually becomes
a Framework.
> 3) Moving something from "not a KDE Framework" to "KDE Framework" gives
> a last chance for fixing up abi/api.
If you need to fix the ABI, you should just bump the soname major version.
I'd just use libKF5*.so.0 (instead of the normal .5) for libraries that are
not yet Frameworks.
Kevin Kofler
