Naming scheme for Qt5/KF5-based libraries outside of KF5

[Kevin Kofler]

Friedrich W. H. Kossebau wrote:
> Given the high standards and required ABI stability there is a good chance
> that some API brush up (e.g. due to review feedback while proposed as KF5
> lib) is made before turning into a KF5 lib, as was already pointed out by
> Sune. Having the same name would prevent that (for the usual problems with
> ABI changes).

Not if you ship your not-yet-in-KF5 library with a soversion (soname major 
version) < 5. (I'd just pick 0.)

        Kevin Kofler