On Wed, Jan 11, 2012 at 6:36 AM, Malvern Star
Consistently functional, when it comes to udpates, should be *the* single overriding concern. If your updater is broken, users can't apply the updates necessary to fix it when you do actually release them!
The YaST updater is good and reliable, no question. The only minor issue I have with it from a user perspective is that when software stack updates come out, it *looks* like no updates are selected, when of course only the software stack update is selected. This may cause the user to start selecting the unticked updates, thinking they have not been automatically selected by accident (I know because not only have I done this myself once, but some of my users have as well). Attempting to apply this update, with the software stack and all the other updates manually selected caused some rather broken behaviour and I ended up having to re-install the system as I recall.
But other than that, yes, the YaST updater has always been my first preference.
The question is who is going to maintain it. It is a lot easier to maintain a single compatibility back-end than an entire GUI programs, or more likely multiple GUI programs since Gnome users are not going to want to pull in a lot of KDE just to do an update. The original maintainers are not willing to do it anymore, and I would rather not add even more work to the KDE team who already has enough on their plate. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org