Comments on: Writing first YCP program

By: Martin Vidner

Martin Vidner — Thu, 19 Feb 2009 11:53:18 +0000

Ugh, I forgot. If you are not root, you will need to call it with the full path: /sbin/yast2 ...

By: Martin Vidner

Martin Vidner — Thu, 19 Feb 2009 11:51:50 +0000

You can also do it without the symlink: yast2 --qt ./PushButton.ycp, yast2 --gtk ./PushButton.ycp, yast2 --ncurses ./PushButton.ycp And if people got interested, here's a page with useful links about YaST development

By: Robin

Robin — Fri, 13 Feb 2009 15:17:42 +0000

well, you never stop learning when using linux, that’s why I love it

By: Alexander Orlovskyy

Alexander Orlovskyy — Fri, 13 Feb 2009 14:12:11 +0000

Robin,i understand , i edited my blog ,so now it makes sense. 😉
Don`t forget,i still learning .

By: Robin

Robin — Fri, 13 Feb 2009 13:34:41 +0000

sure, but exporting a variable and exiting immediately afterwards does nothing.

from the wiki:

export Y2DEBUG=1
yast2

That would start yast2 with the Y2DEBUG variable set to 1.
export Y2DEBUG=1
exit
will set the variable and exit the shell which just discards the variable.

You might want this:
export Y2DEBUG=1 # once in your shell session
…
./y2base ./PushButton.ycp qt

By: Alexander Orlovskyy

Alexander Orlovskyy — Fri, 13 Feb 2009 12:00:31 +0000

Hi Robin, please refer to YaST manual
“The y2logs don’t seem to show my problem. Can that logging be made any more verbose?”

http://en.opensuse.org/Bugs/YaST

By: Robin

Robin — Fri, 13 Feb 2009 11:36:06 +0000

> $ su
> $ export Y2DEBUG=1
> $ exit

That does exactly… nothing.

Exporting variables only affects child processes