Somewhat of an offtopic question, but I ask this because I'm trying to
create a debian package for distributing out a cfengine upgrade from
2.1.13 to 2.1.19p1.
I've compiled cfengine with the following
./configure --bindir=/root/debs/cfengine/var/cfengine/bin
--sbindir=/root/debs/cfengine/var/cfengine/sbin
--datadir=/root/debs/cfengine/usr/share/
--sysconfdir=/root/debs/cfengine/var/cfengine/inputs --localstatedir=
/root/debs/cfengine/var/log --infodir=/root/debs/cfengine/usr/share/info
--mandir=/root/debs/cfengine/usr/share/man
--with-berkeleydb=/usr --with-openssl=/usr --with-docs --with-pcre=/usr
I make and then I make install
The hierarchy that I want ends up in /root/debs/cfengine as I want.
I package it up using dpkg with dpkg --build /root/debs/cfengine
cfengine_2.1.19p1-1_i386.deb
So my question is does the hardcoded path end up being referenced in the
binary later? So will a cfagent binary compiled as such expect to find
/var/cfengine/inputs in /root/debs/cfengine/var/cfengine/inputs or are the
compilation flags simply.
Forgive my ignorance, I have a liberal arts degree and I'm faking my way
through all this stuff...
I can't imagine I'm the only person who has ever dealt with this?
Thanks for all of the help.
Brian Seppanen
608.826.1464
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
http://cfengine.org/mailman/listinfo/help-cfengine
