On Mon, Dec 13, 2010 at 06:44, Adrian Tofan <tofan.adr...@gmail.com> wrote:

> thank you for advice.   Unfortunately I didn't managed to do what I planed. 
> In fact I tried using Debian pinning which allowed me to upgrade ruby gems 
> using the -t option (manualy). -t was needed and I didn't managed to avoid it.
>
> Unfortunately Debian's runbgems is highly modified. Using the upgraded 
> rubygems I couldn't install a gem called buildr only if I manually installed 
> each of his dependencies(more than 15 gems) in order to have the proper 
> version.
>
> All this took me one and half days of work (I am a Debian beginner). I am not 
> sure if Debian's policy is the good one, but it doesn't work for me. I simply 
> may not have the necessary skills for the moment.

It is, in essence, a conflict between the Debian policies and the Ruby
Gem policies, on which there is sadly no clear resolution at present.
:/

> In the mean time I modified my bootstrap script in order to install ruby and 
> rubygems from source (without apt-get). I really hope that a cleaner solution 
> exists and I am looking forward to find it ;)

That *is* the cleaner solution, if you are willing to accept using a
private Ruby.  Debian set aside a bunch of areas, like /usr/local and
/opt, in which you can easily drop this sort of local software with
the assurance that it will not conflict with upstream software.

Resolving the Debian Gem issue is hard, so I would suggest you
continue the policy of a local source install of Ruby and gems, which
you can then use with your application.  (Alternately, you could use
something like rvm to automate parts of this process for you. :)

Regards,
    Daniel
-- 
✣ Daniel Pittman            ✉ dan...@rimspace.net            ☎ +61 401 155 707
              ♽ made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

Reply via email to