libmm-qt/libnm-qt as KF5

[David Faure]

On Monday 07 April 2014 09:47:43 Jan Grulich wrote:
> You are still talking about users, but I'm sure that 99% of them will
> install it from distro repositories and because e-c-m is build dependency,
> they won't notice that. For remaining 1% of users you are talking about
> will be e-c-m available from distro repositories as well, so what's the
> problem? Now those libraries are compiled mostly because of Plasma NM,
> which requires unreleased versions (i.e. for frameworks version) and in
> this case they have already e-c- m installed.
> 
> I don't want to have libnm-qt/libmm-qt as separated libraries, I think that
> a lot of distributions have them in their repositories, because they are as
> dependency for Plasma NM. I would be really interested how many
> distributions would have it without Plasma NM. It makes sense to me be part
> of KF5, don't be separated and be more visible and available for other
> developers and users and probably less confusing for packagers.

I agree. ECM is a very tiny dependency to have, and in return it solves a 
large number of issues for you (deployment, cmake config files, qmake .pri 
file, dependency handling for users of your libs, forwarding headers, 
versioning, releasing, etc. etc.).

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5