Branch: refs/heads/master
Home: https://github.com/yast/yast-ruby-bindings
Commit: c5c6b67a1b4225b4f7ffb8f135ef1dcee74e91ff
https://github.com/yast/yast-ruby-bindings/commit/c5c6b67a1b4225b4f7ffb8f135...
Author: Josef Reidinger
Date: 2017-05-02 (Tue, 02 May 2017)
Changed paths:
M src/y2start/y2start
Log Message:
-----------
fix calling command line interface (bsc#1033993)
This change require a bit longer explanantion. The bug is result of
two changes. The first one is switch to ruby script as start point of
YaST. The second one is bug mentioning that there is different title
after this change. I found that the second one is caused by work-around
in libyui which no longer works. So I decide to do it properly and
always set proper title when starting YaST. And here it hits a bug.
UI in YaST is lazy loaded, it means that it is created when first call
to UI namespace happen. And setting title is that first UI call, so it
creates UI even when command line is required. So this change change
title only if there are no arguments for client. So module is showed in
UI.
Commit: 2b893bcc9b45d701303c3abd4deff9b3a79d2edf
https://github.com/yast/yast-ruby-bindings/commit/2b893bcc9b45d701303c3abd4d...
Author: Josef Reidinger
Date: 2017-05-02 (Tue, 02 May 2017)
Changed paths:
M package/yast2-ruby-bindings.changes
M package/yast2-ruby-bindings.spec
Log Message:
-----------
Changes
Commit: f825272ff7d096d87e4525f6f163969a026c33d0
https://github.com/yast/yast-ruby-bindings/commit/f825272ff7d096d87e4525f6f1...
Author: Josef Reidinger
Date: 2017-05-02 (Tue, 02 May 2017)
Changed paths:
M package/yast2-ruby-bindings.changes
M package/yast2-ruby-bindings.spec
M src/y2start/y2start
Log Message:
-----------
Merge pull request #198 from yast/fix_cli
Fix cli
Compare: https://github.com/yast/yast-ruby-bindings/compare/34912033af9d...f825272ff7...
