System packages work great if you're using system Perl. At work write mostly a Perl shop and system Perl for RHEL 6 is 5.10... So we use Perlbrew and anything > 5.16 (depends largely on the app team).
Also as a general rule I try to avoid modifying the system Perl. With Perlbrew if I muck up the install urns easy to wipe and reinstall Perl, notv true if we're modifying the system Perl. Finally, the system packages tend to lag several versions behind. I know Fedora is more cutting edge than Ubuntu or RHEL, but I didn't think Fedora was shipping Perl 5.18 and whatever the most recent Wx is. I refuse to even attemp a wx install on our Slowaris platforms at work... As to specifics... my biggest issue is I only have to setup Wx once every 6-8 months (so I must be due) so the tricks I used last time are forgotten. That's why a Chef recipe works be perfect because you just add it to a server run last and move on with your day. Thanks, Jon A On May 25, 2014 9:20 AM, "Johan Vromans" <jvrom...@squirrel.nl> wrote: > Jon <three1...@gmail.com> writes: > > > To write a good chef recipe we need to know: "dependancies" or > > prerequisites, what config files are we going to manage, and what > > binaries and libraries are we going to install. Also well need to know > > how to "install" everything on various platforms (dpkg -i vs rpm -i > > etc). > > My main platform is Fedora. The Fedora package build system has an > excellent way of dealing with dependencies. All Fedora releases include > wxperl (perl-Wx as it is called) as a standard package. > I assume Debian and Ubuntu can do this as well. > > What exactly is your problem? > > -- Johan >
