August 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] removing obsolete YaST SVN repo
by J. Daniel Schmidt 26 Aug '13

26 Aug '13

Hi YaST-Hackers, About 15 months ago YaST migrated from SVN to GIT. Since then the old SVN repo was in read-only mode. If nobody objects, I'd like to remove the old svn repo now. So, does anybody still use it or relies on the repo being available? Please tell me by next week. Otherwise I will remove it next Friday. Happy YaST-Ruby-hacking. Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE LINUX Products GmbH Research & Development Maxfeldstr. 5 HRB 16746 (AG Nürnberg) D-90409 Nürnberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- 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] ruby library for manipulation with /etc/passwd and /etc/shadow
by Josef Reidinger 26 Aug '13

26 Aug '13

Hi, I just found quite interesting library[1][2] for manipulation with /etc/passwd and /etc/shadow in quite nice way. Maybe we can use it in yast code if it works good ( so we can reduce our code and benefit from third party code ). Josef [1] http://www.reddit.com/r/ruby/comments/1l2xpe/etcutils_rw_access_to_linux_us… [2] https://github.com/dacamp/etcutils -- 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] Bigger example of tests and possible code reduction with ruby
by Josef Reidinger 23 Aug '13

23 Aug '13

Hi, I just created another pull request[1] that demonstrate how easy can be written test with new framework and what is more important how easy is to modify it ( like add another value to test ). It also demonstrate how can be with ruby simplified code. If you have any question please just ask, so we can see better code on more places. Also you can review if I do not break anything ( you can proof it with test case ). Josef P.S. not recognizing embedded IPv4 in IPv6 is intention as I do refactoring, but after accept of it, I will fix it as it is valid syntax. [1] https://github.com/yast/yast-yast2/pull/106 -- 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] Skeleton or refactored yast module
by Josef Reidinger 21 Aug '13

21 Aug '13

Hi, I am now considering if for documentation purpose is better if we have skeleton or have one really nice plugin that can be used as example. I think about pros and cons and summarize it below. What is your opinion on this topic as it would be nice to have something where we can point new developer who is interested in Yast like when you start you can play generate skeleton and start playing or start with this module and play with it. Skeleton: Pros: - simply - have marks where user should change something Cons: - simply to become outdated or broken as it is not used except new developers ( it actually happen to old one ) Nice module: Pros: - real code, so bigger chance that it contain code that developer need - code is regularly used and tested - real automated tests Cons: - contain module specific code, that is not need to understand Josef -- 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] Simple example of refactoring
by Josef Reidinger 21 Aug '13

21 Aug '13

Hi, because we have now ruby I want to show really simple way how we can refactor existing code. I choose just simple example to be easy to understand and on other hand full working. [1] There is two interesting points in it. 1) using minitest for testing, its structure ( so you can imagine how it looks ) and how it can be easy integrated with automake ( nice part is that if you run `make check` then both testsuite is run, old and new one 2) Using ruby builtin regex, so we no longer need our own. If you have any question I welcome it or if you are interested how do different thing in ruby. Josef [1] https://github.com/yast/yast-yast2/compare/0e08c9b...43fd34e6?expand=1 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

[yast-devel] Help: Lost in Ruby
by Arvin Schnell 20 Aug '13

20 Aug '13

Hi, I would like to use some classes in the converted ruby code but I have problems with function lookup. I have figured out how to call functions (e.g. ArrangeButtons from include/partitioning/ep-lib.rb in my class method by using "module_function :ArrangeButtons" in ep-lib.rb. The problem now is that the method deep_copy cannot be found inside ArrangeButtons. It works if I use "include PartitioningEpLibInclude" inside my class but I don't like to extend the classes with lots of general utility functions. So what's the correct way here? Attached is a patch. The error message is: Client call failed with undefined method `deep_copy' for Yast::PartitioningEpLibInclude:Module and backtrace ["/usr/share/YaST2/include/partitioning/ep-lib.rb:503:in `ArrangeButtons'", "/usr/share/YaST2/include/partitioning/ep-all.rb:183:in `create'", ... ciao Arvin

4 7

[yast-devel] Question Problem with new Hardware
by Günther J. Niederwimmer 19 Aug '13

19 Aug '13

Hello, A fiend have a new Hardware ASUS P9D WS with the new CPU 1150 Socket and the new C226 Chipset. On this Motherboard it is not possible to install oS 12.3 or 13.1 I have no mouse or / keyboard (logitech wireless), is this a YaST2 Problem or a kernel Problem. With older P8CWS, Chipset C216 it is working. Grub2 can handle this Problem? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- 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] Converting YCP data files into YAML, continue removing YCP
by Ladislav Slezak 16 Aug '13

16 Aug '13

Hi all, The ruby conversion did not touch the YCP data files (the files which are installed into /usr/share/YaST2/data and are read using SCR::Read(.target.yast2/.ycp, "foo.ycp") call.) These data files usually contain additional data like hardware databases, additional data mapping... There are several reasons why we did not convert them: - "foo.ycp" in the SCR call would not exist after the conversion, there would be "foo.rb" - .target.yast2 agent parses YCP files, it would fail with Ruby content - Ruby format is not the best format for storing data But to get rid of the YCP interpreter completely (our long term goal) we need to convert these YCP data files anyway. For this reason I have created a simple "ycp2yml" client which reads a specified YCP file and writes it's value into a YAML file. It is included in the latest devtools. It's very easy, it just evaluates the YCP file via SCR.Read, coverts to YAML by calling to_yaml method and saves the result to a file. That means it's not a 1:1 copy, e.g. comments are not transferred, translation marks are lost,... But in many cases it is enough. Of course, you can patch the YAML file manually after the conversion. Example usage: /sbin/yast2 ycp2yml consolefonts.ycp consolefonts.yml Then replace the original YCP file in Git (don't forget to fix Makefile.am and *.spec.in) and use it this way: require 'yaml' # add this if not already there Yast.import "Directory" ... # original code: data = ... SCR.Read(path(".target.yast2"), "foo.ycp") data = YAML.load_file(Directory.datadir + "/foo.yml") rescue nil # nil is the default value if an exception is raised (missing file, # broken/inconsistent, read error...) and is backward compatible. # You can use different default if needed. Note: if you use translations in the original YCP file then you need to use different solution, e.g. convert it into a Ruby file and make it Yast include. You can look at these pull requests: https://github.com/yast/yast-sound/pull/2 https://github.com/yast/yast-ntp-client/pull/10 Enjoy! -- 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

3 4

[yast-devel] Yast Modules: Summer Sale
by Lukas Ocilka 15 Aug '13

15 Aug '13

Hi, I've just announced the *Yast Summer Sale* at this blog: http://kobliha-suse.blogspot.cz/2013/08/yast-modules-summer-sale.html We are offering some great Yast modules for half the price now! If you are interested in having these modules in openSUSE and/or maintaining them, get in touch with us (here or at opensuse-factory). Thanks 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] Introduce Y2DIR "dir" directory
by Josef Reidinger 15 Aug '13

15 Aug '13

Hi, in short, I add in ruby bindings automatic inclusion of "dir" repositories in Y2 paths to ruby load path. Reason is to have common place to have pure ruby private ( in sense of not share it with rest of ruby world ) files. Its intended usage is for various modules, classes and other stuff that makes your plugins nicer. Include directory is not good as it contain now translated code and contain some special magic to make it work in ycp-way. Namespace is shared between plugins so it make sense to use own namespace there same way as in "include" directory. Thanks locilka for initial idea. Long story: For code now there is modules, clients and includes. Modules is intended for modules that share its functionality over component system. You can import it. Clients is scripts, that can be executed by Yast2 environment. Include is tricky as it is code snippets that is internally shared, but it has few limitations - It must be included in code, it must be ensured that it is included only once, so it is very limited compared to ruby ( or perl, python ) ability to share code parts. That leads to idea, that we need directory where you can have proprietary parts of code that is intended only for given module and its usage depends on language. Current status is that it is supported only in ruby-bindings, but plan is also to add it to perl and python bindings, if there is someone who is interested in it (e.g. now in perl it must be all in one file or use some tricky loading or write upstream perl library, that can be called). Example demonstration ( not working, just to demonstrate, real example comes after Milestone 4 ): client C: require "services/main_dialog" data = Services.load dialog = MainDialog.new data result = dialog.run if result == :ok Services.save dialog.data end return result dir/services/main_dialog.rb: require "yast" class Services attr_reader :data def initialize ... end def run ... end end Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 5