
Feature changed by: Mustafa Muhammad (mustafa_muhammad) Feature #318203, revision 7 Title: Let's drop commandline support from Yast Info Provider: Damian Ivanov (damianator) Requested by: Lukas Ocilka (locilka) Partner organization: openSUSE.org Description: Yast provides some kind of a commandline interface which is based on the same functions provided by standard Yast application (Qt, ncurses). Comandline could be used for scripting, but there are already tools that do it better: AutoYast, Chef, Puppet, SUSE Manager, sed (just to name some). Yast commadline has several drawbacks: * not used, not tested, not maintained, too much of obsolete code - too much maintenance for nothing * architecturally wrong - commandline interface to an app that uses commandline tools (e.g., commandline for Services Manager? This is obviously systemctl) * implemented as kind of a hack What do we lose if we remove it? * Possbility for scripting, but as Yast only builds on other cmdline tools or files, there are replacements Another possibility would be to replace commandline with a static information advicing user which tools to use to configure a particular service manually. Business case (Partner benefit): openSUSE.org: Less unused code to maintain == more time to do something that really matters Discussion: #1: Damian Ivanov (damianator) (2014-11-27 13:44:17) -1 if we are to to do that, retire YaST altogether instead. I always liked the cmd version of YaST since often the GUI version crashed if the wrong qt/gtk lib is installed or you fucked up X server. I think though more and more parts of YaST should be retired and replaced by other tools but not specifically the ncurses version. #2: Lukas Ocilka (locilka) (2014-11-27 13:54:53) (reply to #1) Then please summarize what you use Yast commandline for. I personally don't see any reason for keeping it. BTW, we do not want to drop zypper - cmdline tool for software management. #3: Stakanov Schufter (stakanov) (2014-11-28 18:56:59) I have to say I did use it quite successful in the past to repair to errors with nvidia video drivers that did not allow to start any GUI any more. (Speaking of yast from the CLI). As it turned out that for somebody that you have to assist on distance after a crash on the phone, it is far more easy to make yourself understand to that person because of the similarity of what they see with the command line version than to have to tell them correct syntax with zypper, especially when they have to tell you an search what they do have installed. That is not a very "professional" situation, but, for what I see, a far more common case in real life than one may think. I do not say however it is often that I used it. But when I had to use it, it was, IMO, helpful. The more advanced a user will be, the less s(he) will need it, of course. YMMV. + #4: Mustafa Muhammad (mustafa_muhammad) (2014-11-29 08:18:35) (reply to + #3) + Maybe you talking about the ncurses interface, running from the commandline + but acts as GUI: + http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.0/userguide-9.0/ch03s10.ht... + I think this is not about it, it is about the commandline without + ncurses. -- openSUSE Feature: https://features.opensuse.org/318203