We actually need these packages for 6 or 7 different UNIX operating systems, so packaging them wouldn't be much help. We know each of these releases produces a stable build, so it is preferred that we continue to just build these stable releases.
-----Original Message----- From: Aleksey Tsalolikhin [mailto:atsaloli.t...@gmail.com] Sent: Tuesday, May 24, 2011 12:55 PM To: Scott Dobner Cc: help-cfengine@cfengine.org Subject: Re: Lengthy in-line bash commands On Tue, May 24, 2011 at 9:49 AM, Scott Dobner <scott.dob...@sas.com> wrote: > Well it turned out to be a problem with the formatting cfengine was > looking for. What we are trying to do is allow for very easy building > of 3rd party software that we have to build from source. Now what I > am doing is creating small shell scripts that are synced via cfengine > that execute when the software isn't installed. Building on my > original question, is there a better way to build source code, or is > that probably going to be the best option? I have to build about > 30-40 different pieces of software on each host I manage/ Well done on getting this working, Scott! Have you considered packaging the 3rd party software, and then just installing the packages on each host you manage? Are the hosts you manage of the same OS and architecture version? If so, I'd look into packaging. Then you could have Cfengine install the packages. Best, -at _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
