bootstrapping cfengine.

[Russell Davies]

I'm currently in the process of deciding how to install cfengine on
my machines, it seems that simply compiling on the relevant target system
then stashing the binaries somewhere for redistribution to future similar
targets, isn't suffcient since the binaries have other package dependencies
(openssl, berkeleydb).

This means that I have to solve the problem of general file/package
distribution before I even start -- but my intentions were to do this
using cfengine itself, having it look after file distribution to remote
hosts (of which there may be many). This seems to be an ugly circular
dependence.

Obviously this has been solved before, I would like to know how
people went about this and what is generally regarded as the most elegant
approach to getting cfengine up and running, static linking?


r.