Thanks for the reply Matt and Jesse, I accept the reasons (Matt) mentioned for not using source files. I guess the 1st reason I didn't go with rolling up my own .deb fie is that I lack the knowledge to do so, and I'm under a tight schedule for this project so I thought to stick with what I know. The 2nd reason is that I could not believe that Puppet does not support working with source files with a built in mechanism (provider), digging through documentation I realized it does not provide any means to handle source.
I guess I wanted to emulate my current installation method which mixes both apt and compiling packages. I fixed the configure part with adding the path to the binaries mentioned in the error (/bin, /usr/bin). Thanks for all the help, Magic. On Wednesday, January 2, 2013 1:36:29 PM UTC+2, Matthew Burgess wrote: > > On Wed, Jan 2, 2013 at 9:32 AM, <magi...@gmail.com <javascript:>> wrote: > > Hello Everyone, > > > > I'm looking for a way to install packages from source via puppet, I was > able > > to locate maybe 5 posts on this subject which is very strange, as I > would > > expect people to still use ./configure with their own customized > options. > > For example, I need to compile Curl with c-ares support, for that I need > to > > set an option for ./configure but can't find a way to do it. > > I'll get to your actual errors in a moment, but first, I have to ask > 'why'? > > Compiling everything from source on every host just seems really > inefficient. It also will require a compiler and other development > tools on all servers, which isn't generally recommended in a > production environment. > > What is preventing you from compiling your special flavour of Curl on > a development box, and packaging it up using your operating system's > native package management tools (.deb, .rpm, etc.)? Then you can use > puppet to manage the package, rather than as a glorified script > execution mechanism. > > > Debug: Exec[configure](provider=posix): Executing './configure' > > Debug: Executing './configure' > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: 1: > > ./configure: expr: not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: 1: > > ./configure: expr: not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: 95: > > ./configure: as_fn_error: not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: line > 83: > > expr: command not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: line > 90: > > expr: command not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: line > 95: > > as_fn_error: command not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: line > 465: > > sed: command not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: line > 464: > > expr: command not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: line > 465: > > sed: command not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: ./configure: line > 479: > > sed: command not found > > Notice: /Stage[main]/Web_dev/Exec[configure]/returns: : error: cannot > create > > .lineno; rerun with a POSIX shell > > Error: ./configure returned 1 instead of one of [0] > > Error: /Stage[main]/Web_dev/Exec[configure]/returns: change from notrun > to 0 > > failed: ./configure returned 1 instead of one of [0] > > > > Anyone did this or knows whats wrong ? > > Yes, the environment that puppet runs 'exec' statements under is > restricted. You need to set the 'path' parameter to include all the > paths in which those 'missing' executables can be found. See > http://docs.puppetlabs.com/references/3.0.latest/type.html#exec. > > Regards, > > Matt. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Ol6CNoJMrnQJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
