On Thursday 21 of May 2015 12:53:43 Stanislav Baiduzhyi wrote:
On Wednesday 20 May 2015 03:00:24 šumski wrote:
On Tuesday 19 of May 2015 21:07:02 Felix Miata wrote: ....
Why are these K5 NM packages unlikely ever to be of use hard dependencies?
That's a bit of an overstatement ;-)
AFAIK, NM is *always* installed, at least with DVD and LiveCD installs, and is default on laptop installations. The libKF5NetworkManagerQt library is used by the geolocation service in plasma, hence it cannot be avoided. Well, it could be splitted but that's IMHO an overkill, and i personally won't do such split (and probably wouldn't accept it).
That is not entirely true. It is recommended, yes, or maybe even included into base patterns, but you don't have to install it. As hard dependency it appeared only recently, with latest plasma5-workspace update. On the desktop machine with cable and static IP controlled by wicked there is no need in NetworkManager, so I encountered the same issue. I've chosen solution 5 though, breaking plasma5-workspace, but no side-effect or issues so far. So I'd say the dependency is false positive in this case, would be amazing to move it to recommended, but I do not have any strong feelings about it as long as there is an option to break :)
Well, to be honest, i'd rather have every case covered (by requires) than ending up with some users (e.g. those smart ones ;-) which turn off recommends) that need to go into '99 to connect to wireless. If one wants to avoid such deps, which are across distro many many (i don't use gnome but why do i have gtk if i just want a little inkscaping!), best is to install package by package, create custom session files, add needed env variables, adjust LD_LIBRARY_PATH, etc, etc.... Cheers, Hrvoje