Hello all, I've been using AutoYast successfully for a while now (incl. rules), but I never got to understand the purpose of classes or how exactly to use them... (even after reading the documentation about it :-) The docs about rules are quite nice, providing working examples. But for classes, I couldn't find a complete working example/setup. I have the following questions: 1) Until now, I came to understand that classes provide a way to include/merge external XML files. So how are they *different* from a set of XIncludes? 2) If they are different, how does a node know/decide which class it "belongs to" and thus, which XML files it is supposed to merge? Is there some kind of decision process like for rules? The reason I am asking these questions is that I would like to make a modular AutoYast profile XML. Currently, I have one giant_base.xml file plus some small amendments confX.xml, which are merged via rules.xml. My setup looks like this: /autoyast/ |--giant_base.xml |--conf1.xml |--conf2.xml | ... |--confN.xml `--rules `--rules.xml Unfortunately the giant_base.xml became too big to oversee things. What I would like to have is a more or less empty base.xml that simply imports all common parts from sub XMLs (i.e. I would like the partitioning section to have its own file, same with common software, networking stuff and so on). Once all common parts are included, the rules should merge the hardware/host specific changes. It should look like: /autoyast/ |--base_that_includes_common_stuff.xml |`--common | |--common_partitioning.xml | |--common_software.xml | ... | `--common_whatever.xml `--rules | `--rules.xml | ... How would one do this with AutoYast? Thanks for your help :-)