On Tue, Mar 22, 2011 at 01:15:28PM +0100, Uwe Gansert wrote:
no, that can not work. The technical reason is, that autoyast will convert the <result> structure into a map also known as hash. The hash would have the same key ("profile") twice then and that can't work in YCP.
I ran into similar limitations a few years ago and found the way to work around it was to use pre-install scripts that do the same kind of things on the fly. Just output to /tmp/profile/modified.xml (and up to, I think, stock sle10 I found I had to then copy that to /tmp/profile/autoyast.xml due to it re-reading autoyast.xml instead of the modified.xml one). We do a lot of things like... - Determining swap size and any leftover into a /local partition we use, based on ram and a value passed via cmdline. - Networking config parts (we install using dhcp then convert to static based on the hostname lookup in DNS). - Some <package> adds/removes based on the profile (usually adding xen/kvm bits if it's going to be a hypervisor) while still using the default xml files. Pre install is also handy for doing things like saving off existing xorg.conf or ssh keys if they exist then dropping them back in the chroot. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org