libmm-qt/libnm-qt as KF5

[Jan Grulich]

And what is the problem depending on e-c-m? It's the base package, which will 
be available everywhere and being a part of KDE frameworks will make our 
libraries more visible and connected to KDE. We should be definitely part of 
frameworks, like Solid. Well, libnm-qt/libmm-qt are  basically Solid 
libraries. 

Those libraries are reusable, they are basically Qt API for 
NetworkManager/ModemManager, so you can manage connections and devices.

Jan

On Friday 04 of April 2014 05:29 Lamarque Souza wrote:
> Both libraries are meant to be reusable. What I meant with "merge" is the
> fact that the branches "frameworks" in NMQt and MMQt depends on KF5's cmake
> modules. I still want NMQt/MMQt usable for those that use Qt but not KDE's
> libraries (kdelibs and KF5).
> 
> Lamarque V. Souza
> 
> Em 04/04/2014 02:55, "Kevin Ottens" <ervin at kde.org> escreveu:
> > Hello,
> > 
> > On Thursday 03 April 2014 20:19:45 Lamarque Souza wrote:
> > > Well, NetworkManagerQt and ModemManagerQt are Qt only libraries since
> > > the
> > > beginning. They are not meant to depend on any KDE libraries as I said,
> > 
> > so
> > 
> > > they are not meant to be merged to KF5.
> > 
> > Note this is a blatant logic mistake. All the tier 1 frameworks depend
> > only on
> > Qt too, but still they are very much part of KF5.
> > 
> > There might be reasons to not have those two in KF5, but the one you
> > advance
> > is clearly the wrong one.
> > 
> > Regards.
> > --
> > Kévin Ottens, http://ervin.ipsquad.net
> > 
> > KDAB - proud supporter of KDE, http://www.kdab.com

-- 
Jan Grulich 
Red Hat Czech, s.r.o
jgrulich at redhat.com