--===============2160740899184639816== Content-Type: multipart/alternative; boundary="=_2080712561dcb0581c828b84=83e46c12-292f-5da5-ab1f-1d2b237fc8bd_=" --=_2080712561dcb0581c828b84=83e46c12-292f-5da5-ab1f-1d2b237fc8bd_= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable +1 for this.=0A= =0A= On all my computers I'm using openRC and wpa_supplicant to manage wifi = =0A= connections and I don't plan to install Network Manager (nor systemd).= =0A= =0A= Mari=C3=A1n=0A= =0A= ---------- P=C5=AFvodn=C3=AD zpr=C3=A1va ----------=0A= Od: Bernd Steinhauser =0A= Komu: plasma-devel@kde.org=0A= Datum: 26. 5. 2015 10:16:52=0A= P=C5=99edm=C4=9Bt: Dependency to Network Manager / kf5-NetworkManagerQt in= plasma-=0A= workspace=0A= =0A= "Hi,=0A= =0A= since the commit with the id 78c97fin plasma-workspace [1], it depends on = =0A= NetworkManagerQt and hence on Network Manager unconditionally. The use cas= e =0A= outlined in the commit is that the data engine tries to access wlan via = =0A= network =0A= manager to find out which hotspots are around and use that to get location= =0A= informations.=0A= Now apart from the fact that I wouldn't want it to do that and that it = =0A= couldn't =0A= do it on my system, because it uses systemd-networkd for network =0A= configuration, =0A= this results in a dependency on Network Manager.=0A= I do understand that Martin when introducing this commit thought that most= =0A= systems running Plasma 5 will run Network Manager anyway, since that is a = =0A= preferred way of setting up network for many distributions. However, there= =0A= are =0A= many systems, that don't need and use Network Manager and possible don't = =0A= want to =0A= have it installed at all.=0A= Aside from my desktop computer, examples could for example include =0A= workstations =0A= at universities, which often have a static network setup (doesn't matter h= ow=0A= =0A= that is setup).=0A= =0A= So the question is:=0A= Could you make this feature, and therefore the dependency on Network = =0A= Manager, =0A= optional at build time?=0A= =0A= Currently, I just comment out the geolocation dataengine in the =0A= corresponding =0A= CMakeLists.txt and remove the dependency when building plasma-workspace, b= ut=0A= =0A= since I don't know about the code, I can't judge if this has any unforesee= n =0A= consequences, if a data engine is missing.=0A= =0A= Best Regards,=0A= Bernd=0A= =0A= [1] =0A= http://quickgit.kde.org/?p=3Dplasma-workspace.git&a=3Dcommit&h=3D78c97f5b4= 26a1a2dd=0A= 2a9e94de3e482fce9e754ff=0A= Konsole output=0A= _______________________________________________=0A= Plasma-devel mailing list=0A= Plasma-devel@kde.org=0A= https://mail.kde.org/mailman/listinfo/plasma-devel"= --=_2080712561dcb0581c828b84=83e46c12-292f-5da5-ab1f-1d2b237fc8bd_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable +1 for this.

On all my computers I'm using openRC and w= pa_supplicant to manage wifi connections and I don't plan to install Netwo= rk Manager (nor systemd).

Mari=C3=A1n

---------- P=C5=AFvodn= =C3=AD zpr=C3=A1va ----------
Od: Bernd Steinhauser <linux@bernd-ste= inhauser.de>
Komu: plasma-devel@kde.org
Datum: 26. 5. 2015 10:16:= 52
P=C5=99edm=C4=9Bt: Dependency to Network Manager / kf5-NetworkManage= rQt in=0A= plasma-workspace

Hi,

since the commit with the = id 78c97fin plasma-workspace [1], it depends on
NetworkManagerQt and h= ence on Network Manager unconditionally. The use case
outlined in the = commit is that the data engine tries to access wlan via network
manage= r to find out which hotspots are around and use that to get location
i= nformations.
Now apart from the fact that I wouldn't want it to do that= and that it couldn't
do it on my system, because it uses systemd-netw= orkd for network configuration,
this results in a dependency on Networ= k Manager.
I do understand that Martin when introducing this commit tho= ught that most
systems running Plasma 5 will run Network Manager anywa= y, since that is a
preferred way of setting up network for many distri= butions. However, there are
many systems, that don't need and use Netw= ork Manager and possible don't want to
have it installed at all.
As= ide from my desktop computer, examples could for example include workstati= ons
at universities, which often have a static network setup (doesn't = matter how
that is setup).

So the question is:
Could you mak= e this feature, and therefore the dependency on Network Manager,
optio= nal at build time?

Currently, I just comment out the geolocation da= taengine in the corresponding
CMakeLists.txt and remove the dependency= when building plasma-workspace, but
since I don't know about the code= , I can't judge if this has any unforeseen
consequences, if a data eng= ine is missing.

Best Regards,
Bernd

[1]
http://quickg= it.kde.org/?p=3Dplasma-workspace.git&a=3Dcommit&h=3D78c97f5b426a1a= 2dd2a9e94de3e482fce9e754ff
Konsole output
__________________________= _____________________
Plasma-devel mailing list
Plasma-devel@kde.org=
https://mail.kde.org/mailman/listinfo/plasma-devel

= = --=_2080712561dcb0581c828b84=83e46c12-292f-5da5-ab1f-1d2b237fc8bd_=-- --===============2160740899184639816== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUGxhc21hLWRl dmVsIG1haWxpbmcgbGlzdApQbGFzbWEtZGV2ZWxAa2RlLm9yZwpodHRwczovL21haWwua2RlLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL3BsYXNtYS1kZXZlbAo= --===============2160740899184639816==--