Re: Getting $(allclasses) into a shellcommand

[Ed Brown]

You could define groups of rpms, (using yum groups, apt-get groups,
comps.xml, your own flat text files, whatever...), define a class
corresponding to a GROUP of rpms if any rpm in that group is missing,
and let your wrapper script take it from there.  $(allclasses) is
manageably shorter, and hopefully the hundreds of rpms are easier to
manage as well.

If this is a single group of rpms, common to all your systems, install
them at kickstart, and save having to check for them every time cfengine
runs.  

-Ed

ps. It would indeed be great if 'packages:' allowed for executing
actions, rather than just defining classes.


On Thu, 2004-07-15 at 12:16, Chip Seraphine wrote:
> I have some truly enormous $(allclasses) strings as a result of using 
> cfengine 
> to maintain my RPM distributions.  (If you define one 15-to-25 character 
> class for every RPM you need installed, and you need a few hundred RPMs right 
> after a clean kickstart....)
> 
> Anyway, I am having issues passing these large lists of classes into the perl 
> script that does the actual RPM installation.   Mark enlarged a buffer 
> somewheres when I had this problem earlier, but said buffer has been 
> outgrown...    I'd like to find a Proper Solution to this.
> 
> What is a better way than "/some/command $(allclasses)" for doing this sort 
> of 
> thing?  Is there some kind of iterator-type trick  anybody knows?