Attributes for packages pulled in by Packages plugin's prereqs

[Jack Neely <[email protected]…>]

I need to be able to add attributes to the packages that the Packages plugin prereq generator adds to my configuration.

For example, my configuration includes the "sendmail-cf" package. The Packages plugin automatically adds the "sendmail" package as its required by "sendmail-cf." I manage in my configuration /etc/mail/sendmail.mc which sendmail will use to recreate the sendmail.cf with the sendmail-cf package installed.

However, Bcfg2 insists that the "sendmail" package fails verification because /etc/mail/sendmail.cf has been modified and I'm not directly managing that file. I'd really like to not verify the sendmail package or be able to tell Bcfg2 to ignore the /etc/mail/sendmail.cf file.

A suggested method was to use BoundPackage to set verify='false' but this method just adds a second sendmail package to the configuration and does not affect the attributes for the package added by the Packages prereq generator.

[Jack Neely <…>]

Desai's patch to make the Packages plugin also include information from the BoundPackage? tags in the specification solves about 98% of this issue. I can now add attributes to control verification and such to packages that the Package plugin brings in as prereqs.

However, I still have a case where Packages brings in prereqs that are virtual. (A differently named RPM package uses the Provides: tag)

As the virtual package doesn't exist the Bcfg2 client still attempts to verify and marks that package as incorrect even though I have a BoundPackage? entry to turn off verification for that virtual package. I need to get Bcfg2 to know what to do in this situation.

[desai]

I added some code to change the generation of the modified file list to include all paths in all bundles, which should resolve this issue on newer clients.