IMHO, stick with the provided RPM. Its nice that Cfengine delivers this to the Linux folks, and I wish more pre-built packages for other Unix O/S’s are available.
If you use the provided bits, it provides a known baseline for submitting bug reports. When we have to compile, we’re building against various versions of dependencies, which introduce new variables into how the software behaves. The shipped RPM comes with the needed libraries (libpcre, libdb, libgcc, etc.) to make the stack work, on known versions of these dependencies. I would personally focus my time in building out the config management / infrastructure to solve your problems, and stay away from compiling if possible. Just my $0.02. I understand the “I don’t know what code is really being shipped here” argument from accepting pre-compiled binaries, but then again, unless you are a few select developers who actually maintain this project, you aren’t going to comprehend what is contained in the source code anyways. Cheers Mike On 1/27/11 10:38 AM, "Frans Lawaetz" <fr...@broadinstitute.org> wrote: Is it possible to get the spec file that is used to create the RPM I currently download from the engine room for the free version of cfengine. I would rather roll my own RPM's, however i do not want to attempt to reinvent the wheel creating a new spec file. Or even letting us download the src rpm would work well too. I don't believe cfengine makes SRPMS available. I've seen evidence of people creating their own on this list so you might want to dig around and ask for a copy. ________________________________ _______________________________________________ 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
