On 04/02/2016 11:46 AM, Yamaban wrote:
What is the sense in "require/recommend"-ing what whole wifi stuff on a cable only machine? -- I would take the installed packages, but they interfere with normal cable-only operation.
Well there is that! We can probably define a whole class of machines that don't and never will use wifi, not for that matter need monitoring of hot-plug devices, be they USB sticks or additional Ethernet ports. We might call them 'servers' of some sort. We might see data centres with racks and racks of them in rows. We might see billion-dollar companies deploying this and their tech guys wondering why cpu cycles are being wasted on things that the 'servers' don't need. I mean, after all, how often do those machines get rebooted? Especially now with the ability in 4.x to patch live kernels, that Novell and others are crowing about? OK, so some people don't and don't care, but if we don't care why are we discussing it? There is also, as previously mentioned, the massive dependency of KDE on the modem stuff. It is unclear if that is a RPM alone dependency or an actually code level dependency. One of the principles of good systems design is to reduce the level of coupling of modules. How much of this is really necessary? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org