Hello,
On Sep 3 15:18 Josef Reidinger wrote (excerpt):
On Tue, 3 Sep 2013 14:41:40 +0200 (CEST)
Johannes Meixner <[email protected]> wrote:
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?
Or is there a special command line option so that
"yast -i <package>" would not launch any user interface?
Special is that it is expected to by non-interactive call to install
someething. If you place popup here, then you force user to do some
interaction ( and it doesn't work in script anymore ).
I do not understand your respose.
Don't you read or do you misunderstand what I wrote?
Did you really try out how it currently works up to 12.3?
Currently (up to 12.3) "yast -i <package>" is an interactive call.
Accordingly I suggested a popup with timeout that does a reasonable
fallback operation when there is no user interaction so that it does
not enforce user interaction. I explicitly mentioned in my other mail
that this way it will even work in scripts.
Currently "yast -i <package>" does not work in scripts
when <package> cannot be installed: Try out "yast -i qqqq".
Currently this hangs up with a popup that does enforce user
interaction (user must click [OK]) - at least this is how
it behaves on my 12.3 system.
All you would need to do is to acutally run
# yast -i qqqq
versus
# zypper in qqqq
and compare how they behave.
It depends on POV what is documented behavior. For me it is install
package X without my attention and not open sw_single,
This is not what actually happens on SLE11 and up to openSUSE 12.3
(at least on my SLE11 and 12.3 systems).
If there is nothing special documented regarding UI, then (from my
point of view) the current actual behaviour defines that.
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
