On 04/25/2013 01:30 PM, Josef Reidinger wrote:
On Thu, 25 Apr 2013 13:21:29 +0200 Thomas Fehr <fehr@suse.de> wrote:
On Thu, Apr 25, Jiri Srain wrote:
Hi,
(sorry for top-posting)
Unfortunately, reading is not the only operation with the data - YaST also writes them quite extensively.
I don't really know what exactly the problem (internally) is, anyway, I have one suggstion:
Does reading/writing of the AutoYaST profiles, installation workflow definition and similar files work?
If it does, I don't see any reason not to use this YaST-specific XML. It can hold any YCP structures and also the conversion of existing data should be rather simple.
BTW: AutoYaST itself is also using writing and reading ycp file (e.g. /var/adm/autoinstall/cache/autoinst.ycp) and does not only use xml data.
Tschuess, Thomas Fehr
Well, from my point of view we have here two cases. The first one is pure data, that is just read. In such case I think we should consider a well known common mechanism to serialize/deserialize data to file like XML, YaML or JSON. The second case is more interesting. It is ycp that do something, so in fact it is code that write code. In such case we can use serialization of code to XML, but I think it will be more useful to write such code directly in ruby ( or perl or whatever ). But the second case sounds wrong for me, as it allows hard to debug bugs, and we should avoid it as much as possible.
Also remember that you will need an automated migration of the data - and this will probably need to be shipped with new YaST. Jiri -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org