On Mon, Apr 25, 2011 at 10:10:40, Rainer Meier wrote: > So if you want all hosts to have the same set of default packages just > do something like: > > <profile id='default'> > <package package-id='package1' /> > <package package-id='package2' /> > </profile> > > <profile id='profile1'> > <depends profile-id='default' /> > <package package-id='package3' /> > </profile> > > <profile id='profile2'> > <depends profile-id='default' /> > <package package-id='package4' /> > <package package-id='package5' /> > </profile> > ... > > As all profiles have a dependency on the "default" profile this makes > WPKG "include" the defintions in the "default" profile into the scope > of profile1 and profile2. So if you update something in the "default" > profile it will affect profile1/profile2-hosts too. I have our profiles setup this way but on occasion it would be nice to be able to EXCLUDE a default packages without creating/maintaining any entirely new profile. Is there any way to exclude packages? Using your example above, it would be nice to be able to do something like: <profile id='profile3'> <depends profile-id='default' /> <blockpackage package-id='package1' /> </profile> I have over 10 packages in my default profile and every now and then we have a special case where we don't want to install one of the default package on a host (or batch of hosts). Thanks, Andrew |