Mailinglist Archive: yast-devel (144 mails)

< Previous Next >
[yast-devel] quick fix of build failures
  • From: Martin Vidner <mvidner@xxxxxxx>
  • Date: Wed, 20 Feb 2008 16:26:59 +0100
  • Message-id: <20080220152659.GC4706@xxxxxxxxxxxxxxxx>
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
Index: libyui/src/YUI.cc
===================================================================
--- libyui/src/YUI.cc (revision 44681)
+++ libyui/src/YUI.cc (working copy)
@@ -136,6 +136,9 @@

void YUI::ensureUICreated()
{
+ return; // quick fix[TM]
+
+
if ( _ui )
return;

Index: libyui/src/YUILoader.cc
===================================================================
--- libyui/src/YUILoader.cc (revision 44681)
+++ libyui/src/YUILoader.cc (working copy)
@@ -26,6 +26,8 @@

void YUILoader::loadUI( bool withThreads )
{
+ return; //quick fix[TM]
+
const char * envDisplay = getenv( "DISPLAY" );

if ( envDisplay )
< Previous Next >