|
From: | Christian Pearce |
Subject: | blastwave.org cfengine |
Date: | Mon, 09 Aug 2004 19:14:02 -0400 (EDT) |
My general feeling is the package will install in /opt/cfw with a standard configure --prefix=/opt/cfw. I will make every attempt at a complete build. My general feeling is everyone should have an update.conf file that pulls the necessary binaries into /var/cfengine/bin. That way when we use cfengine to upgrade the package we are not at a loss when the package is uninstalled.
Does anyone have any reservations to this approach. Or a better method of doing it? I am all ears. If not I am going to forge ahead. Worse case scenario I can change it down the road. But I would hate to do that if we already commited to something in the field.
I might add that I will not be building it statically. But there will be a run path of that will point to the DB and SSL libs. This will be provided by the blastwave.org packages. The Cfengine package will depend on those packages. Good stuff, enough said.
-- Christian Pearce http://www.commnav.com http://www.perfectorder.com
[Prev in Thread] | Current Thread | [Next in Thread] |