September 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] Please open up "New SLE12 Installer Development" Trello board
by Martin Vidner 05 Sep '13

05 Sep '13

Hi, in the team currently working on refreshing the YaST installer for SLE 12, we've realized that we do too much stuff behind closed doors (again!) and want to fix that. Item: https://trello.com/b/kro7Ng1K/new-sle12-installer-development should be visible to the public (and we should give write access to whoever wants to collaborate). Jsrain, can you as the board admin do that? -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[yast-devel] Whitespace checking (via gitattributes)
by Martin Vidner 04 Sep '13

04 Sep '13

Hi, as you know, our Ruby style guide prescribes that no tabs be used for indentation. (A very practical rationale is that GitHub reviews display tabs at 4 columns instead of the Only Correct Value 8, and code then looks misaligned.) https://github.com/SUSE/style-guides/blob/master/Ruby.md#code-layout To help you with keeping this rule you can use the attached file. Git commands showing diffs will then highlight initial tabs. (I am also looking into editor settings, checking other style guide aspects, and maybe automatic checks for pull requests, but I don't have anything for general use yet.) -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[yast-devel] RFC: Drop yast2 sw_single CLI interface
by Josef Reidinger 03 Sep '13

03 Sep '13

Hi, I would like to drop yast2 sw_single CLI interface because zypper already do such job much better and if we drop it, then it simplify code and we have only one recommended solution which we need to maintain. Any comments, suggestion or complain. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

8 15

[yast-devel] unit tests for yast modules written in ruby
by Roman Neuhauser 02 Sep '13

02 Sep '13

hola! vlado brought up an interesting topic, namely the choice of a unit-testing framework. there's a bunch of them written for ruby code, some of the most popular ones (presented in no particular order) are: * minitest http://rubydoc.info/gems/minitest/frames * rspec http://rspec.info/ * shoulda http://rubydoc.info/gems/shoulda/frames * Test::Unit http://www.ruby-doc.org/stdlib-1.9.3/libdoc/test/unit/rdoc/Test/Unit.html see https://en.wikipedia.org/wiki/Unit_testing_frameworks_for_Ruby for a pretty good overview. i have no strong preference or dislike for any of them, with the exception of rspec, which creates methods on the CUT (to be clear: i don't like that). but before we dive into a massive flamewar re: which one is the best, there's another topic to chew on: do we need to standardize this at all? as far as i understand the situation, yast modules are mostly silos with one or two people ever hacking on any given module. this arrangement would lend weight to the argument that no, we don't need to standardize on a single unit-testing framework, each maintainer is free to choose whatever they like most. OTOH, strong code-ownership has its downsides, so maybe, unless we want to make the segregation of interests stronger, we should not move the code further apart. a standard test framework would make it easier to move code between modules, eg. utility functions initially written for a specific yast module getting promoted to ruby-bindings or something. opinions? -- roman -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 12

[yast-devel] Questions about some YCP Equivalents in ruby
by Thomas Fehr 02 Sep '13

02 Sep '13

Hi, While I was just fixing a bug in current head and had to test the fix anyway I assumed I could easily modify the ruby code needing to be adapted anyway to a more ruby-like style. I replaced the common usage of hash access with default parameter by YCP Code --> Ruby like replacement part["fsid"]:0 --> (part["fsid"]||0) part["type"]:`none --> (part["type"]||:none) substring(part["device"]:"",0,9) --> part["device"][0,9] Could someone with more ruby experience tell me if these replacements are reasonable? My testing showed they work, but I am not sure if there are pitfalls I am not aware of. Tschuess, Thomas Fehr -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr(a)suse.de GPG public key available. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 13

[yast-devel] Ruby based tool for YaST UI for AppArmor
by Kshitij Gupta 02 Sep '13

02 Sep '13

Hello, I started working on developing profile management tools for AppArmor a few weeks ago, the tools should also have a GUI based on YaST. The tools were decided to be developed in Python3 which as I learnt had no bindings with YaST (Python2 does, however I'm told they may have rough edges). So my project mentor (its a GSoC project) cboltz and the devs at AppArmor came up with an idea to develop a Ruby tool for UI based on YaST which would interact with our Python (core) tools via JSON. The idea seemed feasible to us. So, I'd like to know if there's some template or existing code-base we can build upon or use? Any other help/tips/things-to-keep-in-mind would be helpful too. Thanks. Regards, Kshitij Gupta -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1