Hello Anas, I just wonder, why you use saxon for merging the xml files and not the small tool xsltproc contained in the package libxslt. It faster by Magnitutes and also soes not scramble up the Scripts in CDATA as mergeClasses/Saxon does. I use the same merge.xml xslt script: #!/bin/bash xsltproc --param with "'$1'" /usr/share/autoinstall/xslt/merge.xslt "$2" I don't know why, but the '$1' is important! -- Mathias .'\ /. .'.-.-'.-.. ..._: .-. .-. :_... .' '-.(o ) (o ).-' . : _ _ _~(_)~_ _ _ : : /: ' .-=_ _=-. ;\ : : :|-.._ ' _..-|: : : :| |:-:-.-:-:'| |:' : . .| | | | | | |.' .' . -:_| | |_:-' .' -._ ` _.-' -------''
* mk@quara.de <mk@quara.de> [Jul 22. 2002 16:07]:
Hello Anas,
I just wonder, why you use saxon for merging the xml files and not the small tool xsltproc contained in the package libxslt. It faster by Magnitutes and also soes not scramble up the Scripts in CDATA as mergeClasses/Saxon does.
I use the same merge.xml xslt script:
#!/bin/bash xsltproc --param with "'$1'" /usr/share/autoinstall/xslt/merge.xslt "$2"
I don't know why, but the '$1' is important!
At the time when I was testing and libxslt had some problem with CDATA. Now it is resolved and in the next release libxslt is being used. And yes, it's almost 100 times faster :-) Anas
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
* mk@quara.de <mk@quara.de> [Jul 22. 2002 16:07]:
Hello Anas,
I just wonder, why you use saxon for merging the xml files and not the small tool xsltproc contained in the package libxslt. It faster by Magnitutes and also soes not scramble up the Scripts in CDATA as mergeClasses/Saxon does.
I use the same merge.xml xslt script:
#!/bin/bash xsltproc --param with "'$1'" /usr/share/autoinstall/xslt/merge.xslt "$2"
I don't know why, but the '$1' is important!
At the time when I was testing and libxslt had some problem with CDATA. Now it is resolved and in the next release libxslt is being used. And yes, it's almost 100 times faster :-)
There is just one nasty thing: It puts a ns2: in front of each tag name. AutoYaST cannot handle this and stores the ns2: in the YCP-map, so the tags are not recognized. I fixed this with sed, but a real fix would be fixing this in the xml-Agent of YaST2, i guess. -- Mathias .'\ /. .'.-.-'.-.. ..._: .-. .-. :_... .' '-.(o ) (o ).-' . : _ _ _~(_)~_ _ _ : : /: ' .-=_ _=-. ;\ : : :|-.._ ' _..-|: : : :| |:-:-.-:-:'| |:' : . .| | | | | | |.' .' . -:_| | |_:-' .' -._ ` _.-' -------''
* Mathias Kettner <mk@quara.de> [Jul 23. 2002 20:16]:
* mk@quara.de <mk@quara.de> [Jul 22. 2002 16:07]:
Hello Anas,
I just wonder, why you use saxon for merging the xml files and not the small tool xsltproc contained in the package libxslt. It faster by Magnitutes and also soes not scramble up the Scripts in CDATA as mergeClasses/Saxon does.
I use the same merge.xml xslt script:
#!/bin/bash xsltproc --param with "'$1'" /usr/share/autoinstall/xslt/merge.xslt "$2"
I don't know why, but the '$1' is important!
At the time when I was testing and libxslt had some problem with CDATA. Now it is resolved and in the next release libxslt is being used. And yes, it's almost 100 times faster :-)
There is just one nasty thing: It puts a ns2: in front of each tag name. AutoYaST cannot handle this and stores the ns2: in the YCP-map, so the tags are not recognized. I fixed this with sed, but a real fix would be fixing this in the xml-Agent of YaST2, i guess.
Yeah, I know this problem very well :-) This had cost me some time actually and I came up with a very nasty (but working) work-around (not with sed though :-). BTW, We no longer use Qt for XML parsing, instead we use libxml2 which has some nice additional features. For example now you can include external and remote portions of the control file. This means during install you parse the main file and it fetches any included sub-configuration over the net or from the local media. More about this will be in the upcoming release. Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi,
BTW, We no longer use Qt for XML parsing, instead we use libxml2 which has some nice additional features. For example now you can include external and remote portions of the control file. This means during install you parse the main file and it fetches any included sub-configuration over the net or from the local media. More about this will be in the upcoming release.
One other little thing would be very nice: When you merge two xml Files it would be good, that if you have a list-entry with the same name in both of the files that both lists are merged into one list. Considure you have a common base configuration, but want to set for some Computer some additional sysconf variables. All you can do NOW is to replace the whole sysconf section. Unfortunately I don't know how to program XSLT yet :-(
Anas
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
-- Mathias .'\ /. .'.-.-'.-.. ..._: .-. .-. :_... .' '-.(o ) (o ).-' . : _ _ _~(_)~_ _ _ : : /: ' .-=_ _=-. ;\ : : :|-.._ ' _..-|: : : :| |:-:-.-:-:'| |:' : . .| | | | | | |.' .' . -:_| | |_:-' .' -._ ` _.-' -------''
participants (3)
-
Anas Nashif -
Mathias Kettner -
mk＠quara.de