To be clear, I do not think that rbenv or rvm are Good Ideas(tm). I'm
only claiming that there are enough mismanaged ruby code dumps on github
that provide useful functionality that cannot be installed on top of
system rubies without destroying the rest of the system to make rbenv
the lesser evil.
Don't get me started on rvm's
I'll-replace-some-of-your-shell-builtins-with-dynamically-loaded-code-from-the-internets
philosophy.
The ruby community has--obviously with good results--chosen development
velocity over more conservative systems values.
D.
On 07.05.2013 23:35, Brian Lalor wrote:
I'd love to be proven wrong, but in my experience neither rvm nor rbenv are
packaging-friendly. You'll end up compiling code and downloading dependencies
from your prod machines. That's a really Bad Idea.
--
Brian Lalor
bla...@bravo5.org
On May 7, 2013, at 3:55 PM, David Schmitt <da...@dasz.at> wrote:
For everything else, use rbenv or rvm.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
