On Tue, Sep 23, 2014 at 10:25:47AM +0200, Matijs van Zuijlen wrote:
> On 22/09/14 19:01, Antonio Terceiro wrote:
> > On Sun, Sep 21, 2014 at 04:01:21PM +0200, Matijs van Zuijlen wrote:
> >> Not long ago this was easy to do by using rbenv, since it allowed
> >> installing
> >> gems for the system R
On 22/09/14 19:01, Antonio Terceiro wrote:
> On Sun, Sep 21, 2014 at 04:01:21PM +0200, Matijs van Zuijlen wrote:
>> Not long ago this was easy to do by using rbenv, since it allowed installing
>> gems for the system Ruby in a directory in ~/.rbenv. Unfortunately, this
>> feature
>> was broken alon
On 22/09/14 19:16, Christian Hofstaedtler wrote:
> * Matijs van Zuijlen [140921 16:01]:
>> Not long ago this was easy to do by using rbenv, since it allowed installing
>> gems for the system Ruby in a directory in ~/.rbenv. Unfortunately, this
>> feature
>> was broken along with the ability to ha
* Matijs van Zuijlen [140921 16:01]:
> Not long ago this was easy to do by using rbenv, since it allowed installing
> gems for the system Ruby in a directory in ~/.rbenv. Unfortunately, this
> feature
> was broken along with the ability to have more than one system Ruby.
We're now back to having
On Sun, Sep 21, 2014 at 04:01:21PM +0200, Matijs van Zuijlen wrote:
> Not long ago this was easy to do by using rbenv, since it allowed installing
> gems for the system Ruby in a directory in ~/.rbenv. Unfortunately, this
> feature
> was broken along with the ability to have more than one system R
Not long ago this was easy to do by using rbenv, since it allowed installing
gems for the system Ruby in a directory in ~/.rbenv. Unfortunately, this feature
was broken along with the ability to have more than one system Ruby.
Where would gems for ruby-standalone be installed?
Regards,
Matijs
On
Hello Eric,
Thanks for your feedback.
On Mon, Aug 25, 2014 at 12:56:37AM +, Eric Wong wrote:
> Antonio Terceiro wrote:
> > People might solve this type of issue by just using
> > RVM/ruby-build/chruby and not use the Ruby intepreter provided by Debian
> > at all. But then, they have to provi
Antonio Terceiro wrote:
> People might solve this type of issue by just using
> RVM/ruby-build/chruby and not use the Ruby intepreter provided by Debian
> at all. But then, they have to provide security upgrades for the
> interpreter (arguably one of the most sensitive layers of the stack)
> thems
Hello everyone,
It has been a while since I think about ways to make the Ruby stack in
Debian more useful for people who do not want, or can't, use all of it.
For example, some people might might be ok with the version of Ruby
itself we ship, but not with our version of Rails. For example right no
9 matches
Mail list logo
