February 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] buttons buttons buttons
by Martin Schmidkunz 24 Oct '08

24 Oct '08

Hi, when testing openSUSE 11.1/SLES 11 I came across a rather curious situation: many modules have already switched their label from Abort/OK(Accept, Finish...) to the style guide compliant Cancel/OK label. However in every case there is a third, inactive "Back" button included. This doesn't make sense as there is nothing to go back and the dialog is just an overview. I suppose this is due to many of you using wizard.ycp as base template for creating your module. What do you think about using the button box (http://lizards.opensuse.org/2008/08/28/button-order-in-yast-trying-to-make-…) instead of the buttons of wizard.ycp? In my opinion this would have the following advantages: * consistent button order in pop ups and in the module * user would not need to deal with an inactive button * button order in YaST would be consistent with the desktop used by the user What do you think about that issue? Cu, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 6

[yast-devel] 3 questions about yast....
by Roberto Angelino 28 Feb '08

28 Feb '08

OK. First some background: My customer has written a sles9->sles10 live update installation script. I just ran it via ssh. It uses autoyast (the sles10 version) and it installs onto a clean partition (i.e., a partition that isn't running sles9). It works, but they've had to mess with some of the ycp files. Note this script is specialized to their nodes because they only ship 2-3 type of nodes. It's not a general purpose script. Here are the 3 questions they have (for sles10 version): 1) After yast completes installation (i.e., post-install), the fstab is created. What yast module makes this call? It has to be in yast2-installation, but I can't find the connection between the installation and yast2-storage where WriteFstab() lives. 2) How does yast determine what the source partition to mount is? 3) bootloader_finish.ycp breaks the install at the end. They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do? Thanks -robert -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

6 10

[yast-devel] New UI packages and what they do
by Stefan Hundhammer 22 Feb '08

22 Feb '08

Here is a quick overview what all those UI packages are: libyui: The UI core engine. This is what you need to write your own C++ programs (more on that later) that use the UI abstraction. This part is independent of YCP, libycp, YCPValues, liby2, Y2Component, Y2ComponentCreator. It's pure C++. All it depends on are the C++ standard libs (STL) and libpthread (for multi-threading). ycp-ui-bindings: The glue code that make the UI cooperate with the YCP interpreter and with YaST2 as a whole. This is where the UI:: calls in YCP are translated to C++, using the new libyui's widgetFactory to create widgets. This is also the part that uses Y2Component and Y2ComponentCreator to start up the UI and to set up communication with the other parts of YaST2 such as the YCP interpreter, WFM and SCR. Language bindings such as the perl-bindings, python-bindings or ruby-bindings also use this (in particular the YUIComponent, a subclass of Y2Component) to communicate with the UI. We might want to change this in the future to use libyui directly, not going through YCP and YCPValues all the time. qt: The UI plug-in that uses the Qt-libs (Qt4) to actually create widgets. It only depends on libyui (and of course on the Qt-libs), not on YCP, libycp, YCPValues, liby2, Y2Component etc., and also not on libzypp and its dependencies. This is what C++ applications that use libyui are ultimately using, and vie ycp-ui-bindings of course also YCP code (or YaST2 perl modules using the perl-bindings that in turn use the ycp-ui-bindings; similarly for YaST2 python modules). qt-pkg: This contains the package selector for the Qt UI. This is also a plug-in that gets loaded upon demand, i.e. as long as an application does not need a package selector (or a pattern selector or a patch selector), this is not loaded, and neither is libzypp and the libs libzypp depend on. Of course, this package is liked against and depends upon libzypp. ncurses: The UI plug-in that uses the NCurses lib for text mode to actually create widgets. Like the qt plug-in, it only depends on libyui (and of course the NCurses lib) and not on YCP, libycp, YCPValues, liby2, Y2Component, or libzypp. ncurses-pkg: The package selector for the NCurses UI, very similar to qt-pkg. There are still some YCP calls in it, so it currently still depends on libycp and YCPValues, and currently also on ycp-ui-bindings, but we are working on that. CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] UI packages split off yast2-core
by Stefan Hundhammer 22 Feb '08

22 Feb '08

The UI split has now finally happened. We now have separate packages for the UI; the UI is now no longer part of yast2-core: Directory libyui/ -> Packages yast2-libyui yast2-libyui-devel Directory ycp-ui-bindings/ -> Packages yast2-ycp-ui-bindings yast2-ycp-ui-bindings-devel Those of you who build yast2 from SVN might want to do a global "svn up", at least svn up core svn up libyui svn up ycp-ui-bindings Preferably also svn up perl-bindings svn up python-bindings svn up yast2 I adapted the .spec files in all those directories (and also in ruby-bindings which I couldn't test or submit). I also submitted those 6 packages, but coolo wants to hold that change back until after FOSDEM. -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Re: [yast-commit] r44730 - in /trunk/libyui: ./ MAINTAINER RPMNAME VERSION
by Stanislav Visnovsky 21 Feb '08

21 Feb '08

Hi! Dňa Thursday 21 February 2008 12:52:40 sh-sh-sh(a)svn.opensuse.org ste napísal: > Author: sh-sh-sh > Date: Thu Feb 21 12:52:40 2008 > New Revision: 44730 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=44730&view=rev > Log: > skeleton for new package Have you thought about a different name than libyui? I believe the library deserves something better than that ;-) Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Re: [opensuse-factory] yast repositories and software management
by Benji Weber 21 Feb '08

21 Feb '08

On 20/02/2008, Klaus Kaempf <kkaempf(a)suse.de> wrote: > > How much chance is there to be able to call the repository module from > > within the software module? > > Its planned (and looking for community hackers implementing it ;-)) How can one get around the zypp global lock problem? Package selector will obtain a lock on zypp and repository management can't be performed until after it is closed. So displaying them in the same module isn't as trivial as it would appear. AFAIK there's not even a way to release the lock, I ran into this problem when completely random things like requesting the language obtains a zypp lock. -- Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] quick fix of build failures
by Martin Vidner 20 Feb '08

20 Feb '08

With the latest core in autobuild, many testsuites fail, because they cannot get a real UI. But the testsuite explicitly asks for the dummy UI, that does nothing. "y2base foo.ycp UI" means "if foo calls UI:: it just gets nil" Apparently that has been changed into "if foo calls UI: load either qt or ncurses" I think we should revert to the previous behavior, but first let HuHa explain the reasons for the change. In any case, I attach a quick fix that makes the yast2.rpm testsuite pass for me, while still letting the real UI work (on core/libyui/doc/examples/PackageSelector-empty.ycp) -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 2

[yast-devel] `opt(`immediate) for Tree widget
by Stefan Hundhammer 20 Feb '08

20 Feb '08

Arvin suggested to add `opt(`immediate) to the tree widget, too. This is now implemented. `opt(`immediate) is an optimization for the NCurses UI: It makes a widget that has `opt(`notify) set return immediately when its value changes. Normally, the NCurses UI holds such changes back until a special key (typically [Return]) is pressed. For the other UIs (Qt, Gtk) there is no difference between `opt(`notify) and `opt(`immediate) (`opt(`immediate) implicitly also sets `opt(`notify)). Rationale: item-01 *item-02* item-03 item-04 item-05 "item-02" is selected. If you want to select "item-05", in the NCurses UI you have to move the cursor down several times, selecting "item-03" and "item-04" before you can get to "item-05". When `opt(`notify) is set, that widget will make UI::UserInput() return for every event, i.e. the YCP application will receive a ValueChanged event from that widget for "item-03" and "item-04", too. If the YCP application performs expensive operations (like exchanging the items in another list in the same dialog), this can have a considerable performance impact. With this changed behaviour, by default the NCurses UI will not make UI::UserInput() return for "item-03" or "item-04", only when the user hits the [Return] key after he moved the selection to "item-05". With `opt(`immediate), the application will still receive the events for "item-03" and "item-04". For the Qt or the Gtk UI, the application will always receive all events since the user can easily select "item-05" right away with the mouse without having to go through "item-03" and "item-04". Until now, the YSelectionBox and the YTable widgets behaved like this. Now, also the YTree widget behaves like this. Where this is not desired, please change `opt(`notify) for affected tree widgets with `opt(`immediate). But in normal cases, NCurses users will probably prefer better performance. CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Yast2 sw_single crashing on startup in 10.3 (zypp:svn Repository)
by Gryffus 20 Feb '08

20 Feb '08

Hi. Today i updated my yast packages on my 10.3 box and since then i cannot run my yast package manager... I have folowing versions of yast and zypp: libzypp-4.2.6-1.1 zypper-0.10.0-2.1 yast2-qt-2.16.26-3.1 yast2-pkg-bindings-2.16.13-1.6 yast2-qt-pkg-2.16.25-2.5 From zypp:svn repository... When i try to run yast2 sw_single, i get an error: Debug output is here: 2008-02-19 06:21:51 <1> gryffus(7047) [liby2] genericfrontend.cc(main):530 Launched YaST2 component 'y2base' 'sw_single' 'qt' 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(SetLanguage):501 GET encoding for cs_CZ.UTF-8: UTF-8 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Arch) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Confirm) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Label) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Mode) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Popup) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Directory) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (String) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Linuxrc) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Stage) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Installation) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (PackageCallbacks) 2008-02-19 06:21:51 <1> gryffus(7047) [Pkg] PkgModule.cc(instance):68 Redirecting ZYPP log to y2log 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (PackageCallbacksInit) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (URL) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Hostname) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (IP) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (CommandLine) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Report) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Summary) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (TypeRepository) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Address) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Netmask) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (XML) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (RichText) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (SlideShow) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Language) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (AsciiFile) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Encoding) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (FileUtils) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Misc) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (PackageSystem) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (PackageLock) 2008-02-19 06:21:51 <1> gryffus(7047) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (Wizard) 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Import 'UI' failed 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Symbol 'UI::SetModulename' does not exist. 2008-02-19 06:21:51 <3> gryffus(7047) [libycp] Bytecode.cc(readFile):1161 Caught invalid bytecode in '/usr/share/YaST2/modules/Wizard.ybc' 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Loading module 'Wizard' failed 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Import 'Wizard' failed... 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Could not create its namespace 2008-02-19 06:21:51 <3> gryffus(7047) [libycp] Bytecode.cc(readFile):1161 Caught invalid bytecode in '/usr/share/YaST2/modules/PackageSystem.ybc' 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Loading module 'PackageSystem' failed 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Import 'PackageSystem' failed... 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Could not create its namespace 2008-02-19 06:21:51 <3> gryffus(7047) [libycp] Bytecode.cc(readFile):1161 Caught invalid bytecode in '/usr/share/YaST2/modules/Language.ybc' 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Loading module 'Language' failed 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Import 'Language' failed... 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Could not create its namespace 2008-02-19 06:21:51 <3> gryffus(7047) [libycp] Bytecode.cc(readFile):1161 Caught invalid bytecode in '/usr/share/YaST2/modules/SlideShow.ybc' 2008-02-19 06:21:51 <3> gryffus(7047) [Interpreter] clients/sw_single.ycp:21 Loading module 'SlideShow' failed What is wrong here?? Thanx much. Regards Gryffus -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

8 14

[yast-devel] Failing UIs without packageselector packages installed
by Stanislav Visnovsky 20 Feb '08

20 Feb '08

Hi! I've noticed that you finally managed put the packagemanager out of UIs for Qt and ncurses. Cool stuff! However, this makes 'yast2 sw_single' fail in pretty bad way (error message on command line, without a crash dialog, only log reveals the issue). Would it be better if UI report that it does not support the given widget, if the needed .so cannot be found? This way, YCP code can handle the failure gracefully. Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0