On 5/24/11 9:55 AM, "Aleksey Tsalolikhin" <atsaloli.t...@gmail.com> wrote: > 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.
+1 We support a couple architectures now (we're lucky), and I supported a lot more in the past... We still distributed software (internal and third-party) via packages. It really is the right way, even coming from an old Slackware guy. ;) The way it starts is you invest a lot of effort building the packaging infrastructure (which is why some people make the mistake of not doing it, instead spending this effort on other things which won't provide the same ROI), and then after awhile spinning a build for any supported architecture is well documented and easy to do. Yes, even if you get hit by a bus, no one else has to debug your fragile one-off scripts! You end up with a trusted depot of software, creating your DSL in ITIL terms. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
