KR> Is there a way to make this configurable for those that don't want KR> to use Pegasus? This is only for the RPM, of course, and I'm aiming at the Fedora environment. If any other platforms want to use this spec, then we might need to tweak it, however, I'm not aware of any distros that include sfcb. KR> What if you're using Pegasus but you don't have tog-pegasus KR> installed (only sblim-cmpi-devel). If you're using Pegasus, have sblim-cmpi-devel installed, and try to compile the provider (and libcmpiutil) against it, you'll generate broken binaries. However, I don't think that people who have Pegasus installed from source are likely to try to install/build this RPM, as they would have to disable dependency checking. KR> Although, forcing Pegasus users to use tog-pegasus-devel instead KR> of sblim-cmpi-devel is probably reasonable. In the context of a Fedora build, I think we need to explicitly mark packages that will cause broken binaries to be build as Conflicts. We could, however, make the .spec generated with the correct Requires/Conflicts items based on what CIMOM you told configure to use. Perhaps someone more familiar with RPM building could step in here with an authoritative answer. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com