On 04/30/2013 11:47 AM, Klaus Kaempf wrote:
* Martin Vidner <mvidner@suse.cz> [Apr 30. 2013 11:00]:
Or we could write a parser for YCP values (simpler than YCP code) in Ruby.
Take it as an opportunity to clean up the respective parts of YaST.
Once the mechanical translation is done, start by refactoring those code parts that read/write ycp files.
Or we could start doing this in parallel already. Sometimes reading a file might not be needed at all or could use a simpler format than YCP which was selected just because it was the easiest way for us.
Convert these to YaML or JSON. Decide on one representation and use it consistently everywhere. YCP values are sufficiently simple and should not(!) require an XML representation.
Sounds good. Not having XML makes it human-readable and reduces the cost of reading/writing. Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org