Caitlyn, You can use the options --without-libvirt --without-mysql --without-postgresql to disable those features when configuring cfengine.
However, I would suggest reconsidering if the added complexity of splitting CFEngine into multiple packages is worth the potential gains. For example, the CentOS 6 rpm provided at http://cfengine.com/downloads/ is only 4.7MB in size, unpacks to only 13MB when installed, and it contains all the necessary dependencies (including libvirt and libpq), so you don't need to install them separately. Plus you'll have consistency across CFEngine installations, which is a good thing. Given the small size of the CFEngine installation, I personally don't think it's worth the trouble to split it. Best regards, --Diego On Jul 3, 2012, at 2:29 PM, Caitlyn O'Hanna wrote: > Hi, > > I'm trying to make an rpm package for cfengine, but I'm having > difficulty not including libvirt or database components in the main > package and put them in a sub package (e.g. cfengine.x86_64.rpm, > cfengine-libvirt.x86_64.rpm, cfengine-pgsql.x86_64.rpm, > cfengine-mysql.x86_64.rpm) that way I don't have to install libvirt > and postgres (or mysql) on every single machine that will have > cfengine installed on it (i.e., not every server is a database server > or a virtual host). > > > Is there some option that I can enable to get this behaviour? > > > Thank you, > Caitlyn > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
