One thing I will say about that ( at least with RPM ) is that packaging binaries and libraries in out of place locations can become an uphill battle. I've yet to find a clean way of getting RPM to let me have the OS version of something, say curl or perl in /usr, and my own internal one in /usr/local without it becoming a tangled mess.
On Wed, Jan 2, 2013 at 6:36 AM, Matthew Burgess <matthew.2.burg...@gmail.com > wrote: > On Wed, Jan 2, 2013 at 9:32 AM, <magic...@gmail.com> 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 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. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
