On 09/03/2013 02:41 PM, Johannes Meixner wrote:
Hello,
On Aug 30 10:19 Josef Reidinger wrote (excerpt):
On Fri, 30 Aug 2013 10:14:49 +0200 (CEST)
Johannes Meixner <[email protected]> wrote:
On Aug 29 19:44 Rajko wrote (excerpt):
On Thu, 29 Aug 2013 15:36:52 +0200
Ladislav Slezak <[email protected]> wrote:
Starting zypper automatically looks too "smart" for me, I'd leave
the decision to use zypper (or something else) to the user.
Think of it in a different way.
Majority of users are looking for performed operations, not tools
that are used.
If you plan to provide text ready for copy paste, you can issue
warning:
---------------------------------------------------------------------
"yast -i <package>" is depreciated, using "zypper install <package>"
instead.
---------------------------------------------------------------------
and then install package.
This way 99% of users that follow old way, possibly following some
out of date instructions, have nothing to do, and 1% that rely on
some "yast -i" specific behavior have warning if result is not what
they expect.
I think to be really backward compatible, there should be a popup
that informs the user as shown above and waits a specific time for
user accept or deny and if the timeout passed without user response
the default action should be to run "zypper install <package>".
In old YCP one would have used something like
Popup::TimedAnyQuestion() to implement such a behaviour.
Popup in CLI is real pain and I think we should not do it this
way. Complain to stderr sounds better for me.
Can you tell what happens on your system when you call as root
# yast -i <package>
For me both on openSUSE 12.3 and on SLE11 "yast -i <package>"
launches the yast package manager ("sw_single") ncurses UI.
So I like to ask you what would be wrong with a popup
when the ncurses UI runs anyway?
The goal is not to start the NCurses UI and run zypper directly. There
is no reason to depend on YaST.
Also imagine a case when the NCurses UI is not installed.
Jiri
Or is there a special command line option so that
"yast -i <package>" would not launch any user interface?
This way "yast -i <package>" could still work even unattended.
Perhaps some users call "yast -i <package>" in scripts?
This might be of importance for those users that are not yet included
in the 99% and 1% above ;-)
Well, goal of yast -i <package> is install package. Thats what
documentation say, so if user depend on undocumented behavior he must
be prepared that it can change without big noise.
Well, Ladislav Slezak <[email protected]> wrote (see above):
"Starting zypper automatically looks too 'smart' for me"
which means that he would like to change the documented behavior.
So I like to ask you Josef why the documented behavior can be changed
in this case without big noise?
Kind Regards
Johannes Meixner
--
Regards,
Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: [email protected]
Lihovarska 1060/12 tel: +420 284 084 659
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.com
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
