June 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] openSUSE-13.1 Milestone2 with Ruby YaST
by Ladislav Slezak 18 Jun '13

18 Jun '13

[This mail I have sent to opensuse-factory@, I'm posting it also here...] Hi all, Long story short: Alternative Milestone 2 installation images with Ruby YaST created by the YCP Killer project are available here: http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openS… (~3.8GB) http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openS… (~860MB, only package subset, select "Minimal X" or "Textmode" software selection) And here is the full story: Introduction ------------ You might already know the YCP Killer project [1] by which we want to replace our specific YCP language used in YaST by Ruby. The transition to Ruby is automated, we created a translator from YCP to Ruby and improved the core YaST so it can run Ruby modules. Our goal is to switch all our YaST modules from YCP to Ruby in openSUSE-13.1. The most critical part of YaST is the installer which cannot be easily updated on already released media. Therefore we need broader testing before this switch to avoid installation failures on large scale. That's why we created alternative ISO images for installing openSUSE 13.1 Milestone 2 with YaST converted to Ruby. Downloads --------- We have two installation images with converted YaST installer, "fullDVD" which is basically the Milestone 2 DVD ISO and "miniDVD" which contains just a subset of packages needed for "Minimal X" installation (or "Minimal Text Mode", the other software selections will fail because of missing packages). "fullDVD" is recommened, but if your download speed is slow or you have a download limit then you can try the "miniDVD". (Note: we built the ISOs _after_ the official M2 images so there might be some small changes in package versions, the images are not 100% compatible with M2, but they are very close. So rather use the official M2 release for testing and reporting non-YaST issues.) The ISOs are available here: http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openS… (~3.8GB) http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/openS… (~860MB) (We built only x86_64 images to save OBS resources, sorry, no other architectures.) Installation ------------ You need to manually add "insecure=1" boot option because the ISOs are not signed by the official openSUSE GPG key. You will also need to accept the OBS YaST:Head:ruby GPG key when adding the installation repository during installation. Alternatively to full installation you can switch to YaST Ruby later after installing the official Milestone 2. As root run this: # add YaST:Head:ruby zypper ar -f http://download.opensuse.org/repositories/YaST:/Head:/ruby/openSUSE_Factory/ YaST:Head:ruby # replace all YaST packages, use distribution upgrade to allow vendor change zypper dup --from YaST:Head:ruby Then you can test Ruby YaST in installed system, use it the same way as the classic YCP YaST. Testing ------- We already did some minimal testing to ensure the image installs, but we need more intensive testing. So use the images as usual openSUSE installation images, try configuring various system properties, try different hardware/software setups... We only changed the YaST implementation language, so the look&feel of YaST is (or actually must be) the same as in the classic YCP YaST. The automatic translation to Ruby also means that a bug in YCP YaST will be also present in Ruby YaST (bug compatibility). Known bugs ----------- - There is a segfault printed at the console at the end of the first installation stage just before reboot, but it happens at the very end when YaST is exiting and should be harmless. - When using non-English language some texts are not translated (button labels, messages...). - Installation from images is not supported (not available on the medium), the installation proposal will just inform about this. - The ncurses control center in installed system starts for very long time (~2 minutes) For other bugs see the GitHub link in the next section. Bug/Success Reporting ---------------------- We are focused on bugs in YCP to Ruby translation, if you find a bug which is also present in YCP YaST in the official M2 then use the usual bug reporting via bugzilla. If you are unsure you can try the same in the official M2 or you can report it anyway, we will check it. (Of course, it would be nice if you could do that so we are focused on real bug fixing.) Also report slowdowns or other different behavior not observed in original YCP YaST. For reporting bugs use GitHub issues (GitHub account needed): https://github.com/yast/ycp-killer/issues It would be also great to get some positive feedback to know how many people tested our installer and know what has been already tested and works. Just send a short summary what did you test (which module(s), what did you configure...). Feedback -------- If you have any questions or you want to report a success just reply here or connect to #yast freenode IRC channel. Have a lot of fun! Ladislav [1] https://github.com/yast/ycp-killer -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] What about comments for YCP to Ruby conversion?
by Johannes Meixner 18 Jun '13

18 Jun '13

Hello, in http://lists.opensuse.org/yast-devel/2013-05/msg00027.html Ladislav Slezak wrote: ------------------------------------------------------------------------ the converted YaST code currently does _not_ include comments ------------------------------------------------------------------------ Is my understanding correct that the "currently" therein means that it is planned that the generated Ruby code will include the comments from the original YCP sources? If yes, could you tell an estimated date when this will happen? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 6

[yast-devel] Ruby YaST test report (Build0021)
by Ladislav Slezak 06 Jun '13

06 Jun '13

Hi all, I tested openSUSE-Factory-RUBY-YAST-fullDVD-x86_64-Build0021-Media.iso image, here is my summary: - standard installation works (Qt GUI, English, KDE Desktop) - after disabling automatic configuration I got an error in inst_user client in the second stage, looks like a problem in regexpsub() builtin, I'm debugging it right now... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1

[yast-devel] YaST3?
by Ladislav Slezak 03 Jun '13

03 Jun '13

Hi all, with switching YaST into Ruby we reach an important milestone and also do a major change in YaST after many years. So we would like to emphasize this change by increasing the YaST version to number 3. With version 3 we tell all users that there is an important change (although under the cover, look&feel will be the same). And this could be also used as a marketing feature for new products... ;-) There are basically these approaches: - Keep number "2" in the package names, just increase the current version number (e.g. yast2-3.0.0, yast2-packager-3.0.0, ...), but this looks a little bit strange. - Update also the package names to contain "3", e.g. have yast3-3.0.0, yast3-packager-3.0.0... This looks better and uses the old schema. - Remove the number from the package names completely, e.g. have yast-3.0.0, yast-packager-3.0.0... (This would be also future proof as it allows easy switching to version 4 in the far far future :-)) The first solution is the easiest one, we would just need to update the VERSION files. The other solutions need additional support for correct update (additional Provides/Obsoletes in spec files) and would also need extra work for testing updates in real systems (think also of SLE11 upgrades). So there are pros and cons for each solution and therefore I'd like to start a discussion here about the version numbering. What do you think about it? -- 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 To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 6

[yast-devel] YCP vs Ruby: RAM consumption in installation
by Ladislav Slezak 03 Jun '13

03 Jun '13

Hi all, I'd like to extend the David's message about the working installer, I have some interesting data for you. I did some tests regarding the memory consumption in the YaST installer after switching to Ruby because there were some concerns about increased memory requirements... YCP vs Ruby: RAM consumption ============================ Testing setup: HW: VirtualBox virtual machine with 4 CPUs and 1GB RAM SW: openSUSE-12.3, 64bit installation, English language, graphical (Qt) installation. The Ruby installation ISO was from http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/ For YCP installation I used the final 12.3 DVD ISO image. Originally I wanted to put the results directly here, but a spreadsheet document looks better, it's available here: https://docs.google.com/spreadsheet/ccc?key=0ArPH-PKhmo3kdFRFUy05WG50ckpCVH… Summary ------- The overall increase in RAM usage is about 20-30MB (depending on how you measure it). This is not bad if you consider that just the new inst-sys image needs about 5MB more space (because of the added ruby packages). But the converted YaST code currently does _not_ include comments, adding them will slightly increase all YaST files (but should not be much as inst-sys uses compressed squashfs images) Conclusion ---------- The RAM size needed is not much bigger for running YaST in Ruby and the currently needed extra RAM space can be even decreased after some inst-sys tweaking (see the next paragraph) to like 15-20MB more than the old YCP installer. This is really good news! Possible improvements: ----------------------- Currently we include _complete_ ruby in inst-sys, including parts which are not needed for the installer (like webrick web server, test unit, rdoc, rake, xmlrpc, ....). It's possible to remove these parts and save some space in inst-sys which is stored in RAM. It's possible to include just a part of an RPM package to inst-sys instead of complete package. Also the added fast_gettext gem could be filtered to save few kilobytes... Later we could also do some cleanup and use native Ruby library instead of our implementation (e.g. use native net/ftp.rb instead of our FTP.ycp (converted to FTP.rb), the same applies to String.ycp, URL.ycp...) -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 6