On Mon, Apr 29, 2013 at 11:56:06AM +0200, Ladislav Slezak wrote:
Dne 26.4.2013 10:32, Ladislav Slezak napsal(a):
Dne 25.4.2013 16:53, Jiri Srain napsal(a): [...]
The more difficult part will be migration of data created on run-time...
BTW another option is to leave the YCP parser in .target.ycp agent and leave the code as it is now. The agent is independent part of YaST (it just reuses the YCP parser library) so we could leave YCP support in SCR but remove it from the interpreter.
That leaves us with a big(?) amount of C++ code.
We could change the data where possible and leave the complex cases unchanged.
This is still open and we need to actually define how much we want to "kill" YCP...
We already have a parser for YCP data written in Perl: https://github.com/yast/yast-core/blob/master/agents-perl/lib/ycp.pm with tests: https://github.com/yast/yast-core/blob/master/agents-perl/lib/ycp.test so another option would be to call that: Ruby <-> YaST-without-YCP <-> Perl which is, uh, too multilingual I think. Or we could write a parser for YCP values (simpler than YCP code) in Ruby. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu