> > The real pain is the that cfengine requires a non-system version of db > (and libcrypto?) which need to be linked statically because `cfexecd > -L' isn't useful, since cfexecd links them itself. You either risk > distributing binaries which won't load and break the client, or you're > statically linked against an openssl library that may get a security > alert.
I have no idea what this means. Cfengine certainly does not require a "non-system" version of db or lib crypto. They do not need to be statically linked. What kind of nonsense is this? Apologies for this misinformation. Cfexecd -L has nothing to do with static linking, it is for working around broken ldso.conf M _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
