I'm at something of a loss here; I suspect I must be misunderstanding how classes are meant to be used.

I've got three classes - Drive, Site, and Common. I set the last up to contain everything that I would normally put in the standard profile (for all machines).

In the Drive class, I have four XML files, which are all nearly identical; they're meant to switch between installing to hda, hdb, hdc, or hde respectively, with the relevant partitioning information on them. Site contains three classes, for a few site-specific options.

My rules.xml file contains only a few rules. My intent is for it to pick one Drive rule, one Site rule, and the Common rule (I had to have one). So, here's what I have:

I have four of these, all pretty similar. <rule> <disksize> <match>/dev/hde 2000</match> <match_type>greater</match_type> </disksize> <result> <profile>hde.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> ... repeated three more times ... <rule> <custom1> <xinclude:include href="http://xxx/autoinstall/scripts/site.xml" /> <match>Colorado</match> <match_type>exact</match_type> </custom1> <result> <profile>Colorado.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> ... repeated two more times ... <rule> <arch> <match>i386</match> <match_type>exact</match_type> </arch> <result> <profile>common.xml</profile> <continue config:type="boolean">true</continue> </result> </rule>

The profile files hde.xml, Colorado.xml, and common.xml are just there to invoke the classes - it's merely a <classes></classes> section with a reference to just the one class (hdeClass.xml, for example) in it.

The custom script just returns a string containing the name of the site; it works fine (I'll explain why I know that in a bit). Colorado.xml is, like above, a reference to ColoradoClass.xml. I do use a different custom entry for each one, though I wasn't sure whether I needed to or not.

Now, my intent is that I get multiple classes, since multiple of the rules will match, and then AutoYaST will merge the classes. But what I'm getting, if I look in /tmp for the files that it downloaded (or look in my Apache logs), is that it correctly (for my system) downloaded common.xml, hda.xml, Colorado.xml, and commonClass.xml - but it doesn't download hdaClass.xml and ColoradoClass.xml to perform the merge.

Am I misunderstanding how this works? Do I have to set up different profiles that select each combination of classes (and therefore rules with each combination) in order to do this? That doesn't seem right, somehow... what am I missing here?

Thanks for your help...