May 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] Fixing yast2-slide-show for SLE11 SP3
by Karl Eichwalder 16 Sep '15

16 Sep '15

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 7

[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

[yast-devel] Integration of YaST in Ruby into Factory/openSUSE 13.1
by David Majda 31 May '13

31 May '13

Hi, as we are able to install openSUSE-based system using YaST translated into Ruby [1], I would like to discuss now how to proceed with integration of the translated code into Factory/openSUSE 13.1. While we are not ready to do that yet, we think we will be ready relatively soon and thus it makes sense to do some planning & scheduling. In the ideal case, I'd like to get a broad agreement about the plan from YaST developers and then take the discussion to opensuse-factory later this week to see if the plans are OK with openSUSE people. ----- Currently, packages in our testing repository (YaST:Head:ruby) are produced using YCP Killer [2] from YaST module sources on GitHub (we use the master branch in general). I prepare them by periodically downloading the sources, translating them, and committing the resulting package sources to OBS (all that in a dedicated VM). Obviously, this is a transient state. To finalize the work, we need to do two things: 1. Switch master of YaST modules into Ruby (i.e. do the final "official" translation and store its results in Git). 2. Package the translated code and submit the packages into Factory. In theory, these steps are not necessary related. We can switch to Ruby and don't submit anything anywhere. We can also submit the packages still built from YCP source code in my VM. But it is clear both would create lot of problems, so it makes sense to combine these into one big switch. Now let's have a look at the current openSUSE 13.1 schedule: M1: 2013-05-16 M2: 2013-06-13 M3: 2013-07-11 M4: 2013-08-08 B1: 2013-09-19 RC1: 2013-10-10 RC2: 2013-30-31 GMC: 2013-11-08 It's clear that doing the switch in RC phase is too late. Beta also doesn't sound good. On the other hand, we don't think we will have the translator completely ready (= producing code we are satisfied with) until ~2 months from now. That would set the integration point to M4. ** So, our proposal is to aim to integrate Ruby-based YaST in M4.** We'd also like to use M2 and M3 as test-beds and produce our own versions of the images (meaning we'll take exactly the same packages as in M2/M3, replace the YaST ones with Ruby version, and build the image in the same way as official images). We would also like to use the openQA infrastructure to test our images extensively. We think that with this approach we'll be well-prepared for the final integration and we'll minimize the number of bugs and regressions. After M4, there are 3 months until the final 31.1 release. We think this is sufficient time to flush out any bugs/regressions the translation may cause and also to optimize performance and memory usage of Ruby code if this proves necessary. ----- We discussed the proposal above extensively in the YCP Killer team and we think it's reasonable. I'd like to know you opinion about that, as it will undoubtedly affect your work. And ss I wrote earlier, if we reach agreement, I'd like to take the discussion further to opensuse-factory. [1] http://lists.opensuse.org/yast-devel/2013-05/msg00026.html [2] https://github.com/yast/ycp-killer -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 3

[yast-devel] YCP Killer: Factory/13.1 based ISO image available
by Ladislav Slezak 29 May '13

29 May '13

Hi all, we started testing the installer in the YCP Killer project with 12.3 based image with YaST from master. The reason was to have more stable environment which does not change under our hands. But we need to move forward, Factory is the goal. Therefore I have added Factory build target, updated the instalation-images (inst-sys) and adapted the packages added to DVD image to match Factory/13.1 M1 (still not complete, see later). The ISO image is available at http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/ with file name like openSUSE-Factory-RUBY-YAST-miniDVD-x86_64-Build<number>-Media.iso The main differences: --------------------- - Added more packages, the ISO image is slightly bigger (~860MB) - Now you can select Other -> "Minimal X Window" installation which means the 2nd installation stage will run in graphical mode and some more YaST modules will be installed and used during the 2nd stage (like sound, tv card or printer module) - Switched to Ruby 2.0 (as switched in Factory) (You still need to use "insecure=1" boot option.) So if you want to try the latest YaST Ruby installer use this new Factory image since now. I'll soon disable 12.3 images to save some OBS resources. (However, the packages will be still built for 12.3 so you can run the YCP Killer in 12.3.) Thanks! -- 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

1 0

[yast-devel] Package libyui-gtk-pkg Doesn't Build in YaST:Head
by Lukas Ocilka 28 May '13

28 May '13

Hi, All in YaST:Head seems to be green now except one package - "libyui-gtk-pkg" doesn't build in openSUSE_12.3 repository saying: nothing provides libzypp-devel >= 13.0.0 Is that expected? Is that wanted? Thanks in advance Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- 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] YCP Killer: Installer is working
by David Majda 28 May '13

28 May '13

Hi, I would like to announce an important milestone in the YCP Killer project -- we made the installer working. You can download the image that proves it here: http://download.opensuse.org/repositories/YaST:/Head:/ruby/images/iso/ The image is 12.3-based installation DVD with YaST modules from master translated into Ruby. It is able to install a working system. We use a miniDVD for fast rebuilds during development, but a full image will likely work too. Big thanks to Josef Reidinger and Ladislav Slezák who made the installer work! Details About the Image ----------------------- At the URL above there are actually two images -- a continually rebuilt development one and a snapshot of a known working image. We encourage you to try the former as it will generally contain newer code and less bugs. To test the image, you need to boot it with "insecure=1" boot option as the installer is not signed by the official SUSE GPG signing key. During the installation you need to accept the GPG key used in YaST:Head:ruby project. Also note that because the ISO image contains only packages for minimal system, in the Desktop Selection installer dialog you need to choose Other -> "Minimal Server Selection (Text Mode)" for the software selection, otherwise you'll get solver errors for missing packages. Packages & Testing ------------------ Ruby-based YaST packages (used for building the image described above) can be found in the YaST:Head:ruby repository on OBS. Note we successfully translated all packages with YCP code, not only those used in the installer. [*] We'd like to encourage everyone to try Rubyfied YaST2 packages, run them on their systems/VMs, and report any bugs. It would be especially useful if module owners test their own modules, since they know where the tricky parts are and how to test them in the best way. (Disclaimer: While the installer seems to be working but, we do not recommend using the code at production systems with important data.) Any bugs in translated packages (meaning: they don't appear with YCP code in master) should be reported as GitHub issues against the YCP Killer project: https://github.com/yast/ycp-killer/issues The best bug reports are of course those where the reporter is able to debug which Ruby code is causing the bug. The YCP Killer project is also the main entry point if you are interested in the translation. Future ------ So, what we plan to do next? Three things: * Test all translated modules intensely and make sure they run properly. * Make the testsuite run and is green with translated code. * Make the translated code beautiful (so far we only focused on the "make it work" part). We also need to figure out the best way and time to integrate the work into Factory/13.1. I guess you'll see some discussion/e-mails regarding this topic soon. Overall, it seems the project is going well and we are (more or less) on track. [*] We exclude packages that have been dropped and we don't translate some YCP code that will need manual rewrite anyway, e.g. examples/documentation. -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 4

[yast-devel] Let's remove openSUSE 12.2 from YaST:Head
by Lukas Ocilka 24 May '13

24 May '13

Hi, YaST:Head doesn't build for openSUSE 12.2 for an incompatible change done by Marius four months ago: https://github.com/yast/yast-yast2/commit/fa95370c4cd62b26e032b224571f70c45… This makes it impossible for yast2.rpm (and the rest of YaST packages) to build in OBS: https://build.opensuse.org/project/monitor?project=YaST%3AHead Although having 12.2 support would be nice, we probably can't expect new sysconfig package in openSUSE 12.2 so I'm voting for removing that build target. Any opinions or better ideas? If not, I will remove it on Friday. Bye Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 3

[yast-devel] How do I change my Product name while preserving the update path?
by Nathan Cooper 21 May '13

21 May '13

Hey all, I have a YaST product that is being renamed, but we would like to preserve a smooth upgrade path for existing users. Ideally, I would like customers to be able to use "Patch-CD Update" on our new product, and have the following happen: - Old product is automatically removed. Any packages completely unique to the old product are also removed. - New product is installed, and the associated pattern is automatically selected. - Any RPM's that are common between the two products are updated Bonus: - Services automatically updated. Activation codes for the old product services will still be valid with the new product's services and I would like to make the services update as smooth as possible. Currently, I have the new product configured, and it works well for new installations, but the update path is incomplete. I tried adding a "weakremove" line into the new product's release package spec file referring to the old product's release package, but that did not seem to work, as the old product's release package is not automatically removed during the new product's install. What is the best way to perform a product name change while preserving a smooth update path? Here is the short discussion I originally started on the buildservice mailing list: http://lists.opensuse.org/opensuse-buildservice/2013-05/msg00171.html As always, thank you for your help. ~Nathan Cooper -- 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] [PATCH yast-network] Use /etc/hostname instead of /etc/HOSTNAME
by Cristian Rodríguez 20 May '13

20 May '13

--- src/clients/save_network.ycp | 2 +- src/lan/help.ycp | 2 +- src/modules/DNS.ycp | 8 ++++---- testsuite/tests/Network_YaPI.out | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/clients/save_network.ycp b/src/clients/save_network.ycp index 429051d..5a5a0a4 100644 --- a/src/clients/save_network.ycp +++ b/src/clients/save_network.ycp @@ -376,7 +376,7 @@ void CreateOtherNetworkFiles(){ // create hostname if (size(InstallInf["hostname"]:"")>0){ y2milestone("Write HOSTNAME: %1", InstallInf["hostname"]:""); - SCR::Write(.target.string, "/etc/HOSTNAME", InstallInf["hostname"]:""); + SCR::Write(.target.string, "/etc/hostname", InstallInf["hostname"]:""); } if(InstallInf["bootproto"]:"dhcp"=="static") diff --git a/src/lan/help.ycp b/src/lan/help.ycp index 762b6a1..35e1e1d 100644 --- a/src/lan/help.ycp +++ b/src/lan/help.ycp @@ -255,7 +255,7 @@ DHCP servers update name server zones (forward and reverse records) according to this hostname (dynamic DNS). Some DHCP servers require the Hostname to Send option field to contain a specific string in the DHCP messages from clients. Leave AUTO -to send the current hostname (for example, the one defined in <tt>/etc/HOSTNAME</tt>). +to send the current hostname (for example, the one defined in <tt>/etc/hostname</tt>). If you do not want to send a hostname, leave the field empty. "), diff --git a/src/modules/DNS.ycp b/src/modules/DNS.ycp index b4a90c3..6d7499b 100644 --- a/src/modules/DNS.ycp +++ b/src/modules/DNS.ycp @@ -216,12 +216,12 @@ global void ReadHostname() { // the usual location if (fqhostname == "") { - if (SCR::Read (.target.size, "/etc/HOSTNAME") > 0) + if (SCR::Read (.target.size, "/etc/hostname") > 0) { - fqhostname = (string) SCR::Read (.target.string, "/etc/HOSTNAME"); + fqhostname = (string) SCR::Read (.target.string, "/etc/hostname"); //avoid passing nil argument when we get non-\n-terminated string (#445531) fqhostname = String::FirstChunk( fqhostname, "\n" ); - y2milestone("Got %1 from /etc/HOSTNAME", fqhostname); + y2milestone("Got %1 from /etc/hostname", fqhostname); } } @@ -347,7 +347,7 @@ global define boolean Write() { SCR::Execute(.target.bash, "/bin/hostname " + hostname); /* write hostname */ - SCR::Write(.target.string, "/etc/HOSTNAME", fqhostname + "\n"); + SCR::Write(.target.string, "/etc/hostname", fqhostname + "\n"); sleep(sl); /* Progress step 2/3 */ diff --git a/testsuite/tests/Network_YaPI.out b/testsuite/tests/Network_YaPI.out index 6dae320..563b7b4 100644 --- a/testsuite/tests/Network_YaPI.out +++ b/testsuite/tests/Network_YaPI.out @@ -5,8 +5,8 @@ Read .sysconfig.network.dhcp.WRITE_HOSTNAME_TO_HOSTS "no" Read .sysconfig.network.config.NETCONFIG_DNS_POLICY nil Read .sysconfig.network.config.NETCONFIG_DNS_STATIC_SERVERS "208.67.222.222 208.67.220.220" Read .sysconfig.network.config.NETCONFIG_DNS_STATIC_SEARCHLIST "suse.cz suse.de" -Read .target.size "/etc/HOSTNAME" 27 -Read .target.string "/etc/HOSTNAME" "laptop.suse.cz" +Read .target.size "/etc/hostname" 27 +Read .target.string "/etc/hostname" "laptop.suse.cz" Read .target.size "/etc/sysconfig/network/routes" 27 Read .routes [$["destination":"default", "gateway":"10.20.30.40"]] Execute .target.bash "rpm -q --whatprovides SuSEfirewall2" 0 -- 1.8.2.3 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 4

[yast-devel] [PATCH yast-mail] Use /etc/hostname instead of /etc/HOSTNAME
by Cristian Rodríguez 20 May '13

20 May '13

--- src/YaPI/MailServer.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/YaPI/MailServer.pm b/src/YaPI/MailServer.pm index 2051480..005cd5d 100644 --- a/src/YaPI/MailServer.pm +++ b/src/YaPI/MailServer.pm @@ -2387,7 +2387,7 @@ sub WriteMailLocalDomains { my $host = `hostname -f`; chomp $host; if( ! $host ) { - $host = `cat /etc/HOSTNAME`; chomp $host; + $host = `cat /etc/hostname`; chomp $host; if( ! $host ) { $host = 'linux.lokal'; @@ -2983,7 +2983,7 @@ sub activate_virus_scanner { my $mydomain = `hostname -d`; chomp $mydomain; if( ! $myhostname ) { - $myhostname = `cat /etc/HOSTNAME`; chomp $myhostname; + $myhostname = `cat /etc/hostname`; chomp $myhostname; if( ! $myhostname ) { $myhostname = 'linux.lokal'; -- 1.8.2.3 -- 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] [PATCH yast-restore] Use /etc/hostname instead of /etc/HOSTNAME
by Cristian Rodríguez 20 May '13

20 May '13

--- src/Restore.ycp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Restore.ycp b/src/Restore.ycp index ad3391c..ffb1040 100644 --- a/src/Restore.ycp +++ b/src/Restore.ycp @@ -897,7 +897,7 @@ you may find current contact information at www.novell.com "kdebase3" : $["descr" : "KDE base package: base system", "files":["/etc/opt/kde3/share/config/kdm/kdmrc"], "prefix" : "", "sel_type" : "X", "vers" : "3.0-19"], "mozilla" : $["descr" : "Open Source WWW browser", "files" : ["/opt/mozilla/chrome/installed-chrome.txt"], "prefix" : "", "sel_type" : "X", "vers" : "0.9.8-54"], "lprng" : $["descr" : "LPRng Print Spooler", "files" : ["/etc/init.d/lpd"], "prefix" : "", "sel_type" : "X", "vers" : "3.8.5-49"], - "netcfg":$["descr" : "Network configuration files in /etc", "files" : ["/etc/HOSTNAME", "/etc/defaultdomain", "/etc/exports", "/etc/hosts"], "prefix":"", "sel_type":"X", "vers":"2002.3.20-0"] + "netcfg":$["descr" : "Network configuration files in /etc", "files" : ["/etc/hostname", "/etc/defaultdomain", "/etc/exports", "/etc/hosts"], "prefix":"", "sel_type":"X", "vers":"2002.3.20-0"] ]; // set default selection -- 1.8.2.3 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2

[yast-devel] [PATCH yast-yast2] Use /etc/hostname instead of /etc/HOSTNAME
by Cristian Rodríguez 19 May '13

19 May '13

--- library/types/src/Hostname.ycp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/types/src/Hostname.ycp b/library/types/src/Hostname.ycp index a98aa30..65e091b 100644 --- a/library/types/src/Hostname.ycp +++ b/library/types/src/Hostname.ycp @@ -165,7 +165,7 @@ global define string CurrentFQ() { map hostname_data = (map) SCR::Execute(.target.bash_output, "hostname --fqdn"); if (hostname_data == nil || hostname_data["exit"]:-1 != 0 ) { - fqhostname = ($[] != (map) SCR::Read(.target.stat, "/etc/HOSTNAME") ? (string) SCR::Read(.target.string, "/etc/HOSTNAME"):""); + fqhostname = ($[] != (map) SCR::Read(.target.stat, "/etc/hostname") ? (string) SCR::Read(.target.string, "/etc/hostname"):""); if ( fqhostname == "" || fqhostname == nil ) { -- 1.8.2.3 -- 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] fulltime Y2DEBUG=1???
by Roberto Angelino 15 May '13

15 May '13

I have a customer who is asking if it's OK to set Y2DEBUG=1 all the time: When we encounter SLES media problem, one of the first things SuSE engineers ask us to do is reproduce with Y2DEBUG=1 on the kernel commandline. We were thinking about always having this media feature enabled going forward. Can we ask SuSE engineers if there is any cause for concern in doing this? ---- Roberto Angelino Dedicated Partner Engineer Developer Support (310) 529-3527 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 5

[yast-devel] Automatical built of YaST packages
by Thomas Goettlicher 10 May '13

10 May '13

Developers, I'm happy to announce that YaST packages are built and submitted automatically now. For every change of a YaST package located in the git repo's master branch ( https://github.com/yast/ ) the package is build automatically. On success it's submitted to YaST:Head in the build service, otherwise an email on yast-commit(a)opensuse.org informs about the failure. Packages in YaST:Head still need to be submitted to Factory manually because we want to make sure not to break Factory by this automatism. Cheers, Thomas -- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 9

[yast-devel] YCP-killer and YCP data files
by Ladislav Slezak 02 May '13

02 May '13

Hi all, as you know we are working on a "YCP-killer" project, which should translate all YCP files to ruby and then get rid of our specific YCP language. I found a problem related to reading data YCP files. The problem is that some modules have data in YCP files which are read at runtime via these SCR calls: SCR::Read(.target.yast2, "foo.ycp") SCR::Read(.target.ycp, "bar.ycp") We can convert that YCP files to ruby with the converter but the loading mechanism will not not work. And keeping the data files in YCP format is also not an option. There are basically two possibilities: - convert the YCP files to a different format (plain text, YML, XML...) - modify the YCP files so that they can be used as an include file (includes are converted to ruby files so there is no change needed after the conversion) Which solution is better depends on the data in the file, some non-structured data could be simply converted to a plain text file, converting structured data is usually more complex. The second solution is easier for structured data as the file itself can be more or less left untouched, only the loading mechanism needs to be changed to an include statement. The disadvantage of the second solution is that the data is loaded persistently to memory (as it actually becomes code) so for large data files it might not be a good idea. As a proof of concept I adapted two YCP modules and changed the data files to includes, see these pull requests: https://github.com/yast/yast-ntp-client/pull/5/files https://github.com/yast/yast-mouse/pull/2/files The mouse module is little bit tricky as the database contains translations. And they need to be translated dynamically to reflect possible language changes during installation proposal, therefore I added a wrapper function which always returns a fresh instance of the data with the current translations. Conslusion: If you have some spare time and want to help us with the ruby translation you can start removing the YCP data files. You can look at the pull requests above for a hint how to do that. Or just ask here or on the IRC. Thank you! -- 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

8 16