June 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] New Web Yast development tips wiki page
by Ladislav Slezak 12 Jun '09

12 Jun '09

Hi all, I just have added http://en.opensuse.org/YaST/Web/Development/Tips wiki page with Web YaST developments tips. Currently there is described the ruby debugger and there are some tips for useful Firefox plugins. Feel free to enhance the page! -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- 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] YaST used for Filtering the World
by Lukas Ocilka 10 Jun '09

10 Jun '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, YaST has been used as an openSUSE Education configuration tool, see more (including screenshots) here: http://www.jeffshantz.com/?p=40 See also set of screenshots here: http://www.flickr.com/photos/39290324@N06/sets/72157619427547753/ BTW, the maximum age of a person is only 125 years! ;) Bye Lukas - -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) - ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFKL4g5VSqMdRCqTiwRAmkcAJ0bgMXI8LIHlyLbuVVhj2rinTWvPwCeI8Yy p0yl3dTKAf4/zdPmfbWdj0w= =vYF/ -----END PGP SIGNATURE----- -- 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] Question about Python and Ruby bindings
by Jeff Shantz 10 Jun '09

10 Jun '09

Hi all, First off, let me apologize if my questions have already been covered. I searched the archives and Googled for answers, but didn't come up with much. I am developing the YaST education module as part of the Google Summer of Code. I am interested in using the Python bindings, and currently have yast2-python-bindings-2.17.3-1.41 installed on openSUSE 11.1. I created a template using the config-python skeleton, but when I do a make/make install and then try to run my module, I get an error that no such client module is found in the search path (/y2update/clients, /root/.yast2/clients, /usr/share/YaST2/clients). I assume that the problem lies in the fact that a .py file has been installed in /usr/share/YaST2/clients instead of a .ycp file. Do I need to create a .ycp wrapper to load my Python module, or what is the "standard" way? Second question, out of interest. I see that Ruby bindings exist for YaST, but haven't seen much documentation on them except for a few blog posts from 2007. Are the Ruby bindings production ready, or still considered unstable? If these questions are in the wrong list, please direct me to the right place. Thanks all. Regards, Jeff Shantz -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] Czech YaST2 team (Prague) meeting 2009-04-06
by Jozef Uhliarik 08 Jun '09

08 Jun '09

Czech YaST2 team (Prague) meeting 2009-04-06 ============================================ Present: jkupec, jreidinger, jsrain, jsuchome, juhliarik, kmachalkova, locilka, lslezak, mvidner, mzugec, jsuchome Minutes: juhliarik Next Minutes: locilka WebYaST ------------- - the most members of yast team continue to play with RoR - a new skeleton for REST API yast packages has been added to yast2-devtools (lslezak) - a new GEM package (yast2-webservice-tasks) has been created as a part of Web Yast. It will contain shared Rake tasks for all Yast Web packages. (lslezak, mvidner) Misc: ------ - WIP on Qt4 control centre, launching the modules works by now (kmachalkova) - http://mzugec.blogspot.com/2009/05/automatic-installation-via-pxe.html Miso needs some feedback before he will write it to opensuse wiki (mzugec) - yast2-security: pam_pwcheck calls replaced with pam_cracklib/pam_pwhistory, removed obsolete "obscure checks" settings (fate#305468, jsuchome) -- 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] YaST:/Head repo out -of-date (outdated deps on zypp:/Head)
by PGNet Dev 03 Jun '09

03 Jun '09

hi, the YaST:/Head repo has been out-of-date/sync with zypp:/Head for 5+ days. specifically, yast2-pkg-bindings has, apparently (https://bugzilla.novell.com/show_bug.cgi?id=509191#c3), an outdated dep on an old libzypp. as it's been awhile, and makes it impossible to track zypper development, can we please get that repo updated? thanks. -- 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-storage and libstorage
by Arvin Schnell 03 Jun '09

03 Jun '09

Hi, for those compiling yast from svn: libstorage is now a own project and not included in the yast svn anymore. Currently you can find libstorage: - buildservice project YaST:Head package libstorage - git.opensuse.org/project/libstorage ciao Arvin -- 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] Rails convention and WebYast
by Josef Reidinger 02 Jun '09

02 Jun '09

Hi, I found one nice summary article about ruby and rails conventions http://itsignals.cascadia.com.au/?p=7 (added to webyast wiki). I hope this help everyone who is same confused as me :) (and it should be adapted to new developer training kit, because current one use non-convention things which lead e.g. to some cryptic lines in routes config) Josef -- 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] Yast webservice - sharing .rake files
by Ladislav Slezak 02 Jun '09

02 Jun '09

Hi all, I started to implement an example WebYast package and I have a yast2-devtools skeleton for REST API package ready. But I found that many things are duplicated in all REST plugins. E.g. each Rakefile contains the same copied targets (e.g. 'package'). The common targets should be shared instead of copying. If there is a bug or we want to add a new feature we have to fix a lot of packages... Here is my proposal: - Add include.rake file into rakelib[*] subdirectory in each plugin, see the attachment. (It includes the files from the current directory if it's called inside the git repository otherwise it includes system files from /srv/www/yastws/...) - Define the shared tasks in rest-service/webservice/lib/tasks/webservice subdirectory. The tasks should use webservice: namespace prefix so it's obvious that they are defined in the webservice not in the plugin or somewhere else. (See syntax_check.rake example) After that 'rake -T' in a plugin subdirectory will display the syntax check target from the shared directory, no need to copy&paste the code. What do you think about it? Any comments? I'm not a Rakefile expert... [*] I found that tasks defined in 'tasks' subdirectory in plugins are not found by rake, they must be in 'rakelib' subdirectory instead. We have to call 'git mv tasks rakelib' for all plugins and fix the .spec files... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ # import global .rake files for plugins if File.exist? "#{File.dirname(__FILE__)}/../../../webservice/lib/tasks/webservice/" # use delopemnt files if we are in git repository Dir["#{File.dirname(__FILE__)}/../../../webservice/lib/tasks/webservice/*.rake"].each { |ext| load ext } else # use the files from yast2-webservice package Dir["/srv/www/yastws/lib/tasks/webservice/*.rake"].each { |ext| load ext } end require 'rake' namespace :webservice do desc "Check syntax of all Ruby (*.rb) files" task :syntax_check do `find . -name "*.rb" |xargs -n1 ruby -c |grep -v "Syntax OK"` puts "* Done" end end

3 10