https://bugzilla.novell.com/show_bug.cgi?id=216649 ------- Comment #10 from marcio.ferreira@gmail.com 2007-04-19 06:51 MST ------- This procedure cited in comment 9 is not good enough, it will prevent the use of zypper in automated scripts, which is crippling the software. Im aware people can do yess|zypper but thats not a solution, I guess. How about having in some /etc/zypper.conf a flag "allow_zypper_to_run_non_interactively=1" and then maybe explain that in the comments, the licence implications, etc? Or a sysconfig variable, dunno. There are lots of use cases that this is a sensible option, ane because in one use case that it doesnt fit well, this is crippling zypper, spcecially compared to smart and rug. This will push the non adoption of zypper in a niche it should solve the problem. Specially throught people who use command line and think they are so smart and they "Know better", those who think that yast qt is so much faster than yast ncurses, even when we are talking about a complete io-bounded process, like parsing the metadata... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.