[BioRuby] Ruby installation

[Michael Barton]

I have been using Docker a lot. I think it's excellent. The ability to wrap
a program up with it's own environment is very powerful. For example you
can upgrade software to faster, newer runtimes without having to wait to
upgrade the global system runtime.


On 30 April 2014 09:05, Francesco Strozzi <francesco.strozzi at gmail.com>wrote:

> Agreed.
>
> I think VM and Docker are the right way to deal with this, as they offer
> easy and reliable solutions to ship full contained environments that can be
> used for testing, development or even production.
> For the rest, I do see RVM as a good solution and has proven to work well
> during the years. Even for other scripting languages I tend to use RVM-like
> solutions such as PyEnv or PerlBrewer, to create full isolated and
> customized installation of Python / Perl.
> The "mess" that we sometimes experience IMO is more with gems versioning
> and installation and this is mostly due to bundler / jeweler behavior
> rather than RVM et al. Probably the best thing, if the environment is
> difficult to build from scratch, is to pack everything that's needed for a
> certain application into a lightweight container and deploy it.
>
> Just my two cents, of course.
>
> Ciao
> Francesco
>
>
>
>
> On Wed, Apr 30, 2014 at 5:36 PM, Fields, Christopher J <
> cjfields at illinois.edu> wrote:
>
> > FWIW, Perl has been down this road, and I see history repeating itself
> > unfortunately.  I’ve started looking into alternate solutions for these
> > things myself; for perl there is Pinto, but as a more generic solution
> > Docker seems very promising for this:
> >
> >     https://www.docker.io
> >
> > Re: Software Carpentry, they are very much a python/R-driven thing in our
> > experience, for good or bad.
> >
> > Just curious, but is this related to Ruby 1.7->Ruby 2?  I know the Python
> > community is going through a bit of a similar situation with Python2->3
> > transition, in that uptake of Python3 isn’t going so well.
> >
> > chris
> >
> > On Apr 30, 2014, at 8:21 AM, Pjotr Prins <pjotr.public14 at thebird.nl>
> > wrote:
> >
> > > Yes, I am talking newbies.
> > >
> > > On Wed, Apr 30, 2014 at 02:28:51PM +0200, Gianluca Della Vedova wrote:
> > >> Hi Pjotr,
> > >> what's the intended audience (total newbies, new to ruby but with fair
> > >> computer experience, etc.)? Building from source might be suited only
> > >> for experienced people.
> > >>
> > >> Albeit not related to Ruby, IMO the software carpentry group have
> > >> dealing with the same issues for some time (they tend to use VMs for
> > >> teaching, I don't know if that would be fine for your purposes).
> > >>
> > >> My experience with rbenv when I started exploring ruby has been good.
> > >> YMMV.
> > >>
> > >> Best,
> > >> --
> > >> Gianluca Della Vedova
> > >> http://gianluca.dellavedova.org
> > >> On 29/04/2014 at 07:14, Pjotr Prins wrote:
> > >>
> > >>> Hi everyone,
> > >>>
> > >>> It used to be that Ruby was easy to install.
> > >>>
> > >>> But the last years I find people are having real trouble installing
> > >>> Ruby and gems. I also run into odd annoyances, even if I can handle
> > >>> rvm myself. I am running into this because I am teaching people to
> use
> > >>> my gems :). I think it is too hard for a language that is supposed to
> > >>> be easy.
> > >>>
> > >>> Anyone disagree?
> > >>>
> > >>> Can we develop a best practise protocol that works for our gems at
> > >>> least on all Linux distributions? What would be the best way? And
> > >>> maybe we can extend to OSX and Windows later.
> > >>>
> > >>> Homebrew would be nice, but it needs a good Ruby to bootstrap. RVM is
> > >>> too tricky.
> > >>>
> > >>> Do we need to build from source, perhaps? Or start using GUIX?
> > >>>
> > >>> Any suggestions other then use my 'favorite' distribution are
> welcome.
> > >>>
> > >>> Pj.
> > >>> _______________________________________________
> > >>> BioRuby Project - http://www.bioruby.org/
> > >>> BioRuby mailing list
> > >>> BioRuby at lists.open-bio.org
> > >>> http://lists.open-bio.org/mailman/listinfo/bioruby
> > >> _______________________________________________
> > >> BioRuby Project - http://www.bioruby.org/
> > >> BioRuby mailing list
> > >> BioRuby at lists.open-bio.org
> > >> http://lists.open-bio.org/mailman/listinfo/bioruby
> > >>
> > > _______________________________________________
> > > BioRuby Project - http://www.bioruby.org/
> > > BioRuby mailing list
> > > BioRuby at lists.open-bio.org
> > > http://lists.open-bio.org/mailman/listinfo/bioruby
> >
> >
> > _______________________________________________
> > BioRuby Project - http://www.bioruby.org/
> > BioRuby mailing list
> > BioRuby at lists.open-bio.org
> > http://lists.open-bio.org/mailman/listinfo/bioruby
> >
>
>
>
> --
>
> Francesco Strozzi
>
> _______________________________________________
> BioRuby Project - http://www.bioruby.org/
> BioRuby mailing list
> BioRuby at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioruby
>