| 1 |
Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
|
| 3 |
> On Friday 27 June 2014 08:16:08 Hans de Graaff wrote: |
| 4 |
> > On Thu, 26 Jun 2014 23:36:00 -0400, Ajai Khattri wrote: |
| 5 |
> > > !!! All ebuilds that could satisfy |
| 6 |
> > > "virtual/rubygems[ruby_targets_ruby18]" |
| 7 |
> > > have been masked. |
| 8 |
> > |
| 9 |
> > You still have packages on your system that have been installed with the |
| 10 |
> > ruby18 RUBY_TARGET. It's not immediately clear which package that is from |
| 11 |
> > the output, but I suspect dev-ruby/rubygems? Re-emerging the packages |
| 12 |
> > still installed for ruby18 should fix this. |
| 13 |
> |
| 14 |
> Some months ago I found myself wondering why I had ruby on this box at all. A |
| 15 |
> little poking around revealed that the only thing that needed it was thin- |
| 16 |
> provisioning. Once I'd added -thin to my USE flags and recompiled lvm2 I could |
| 17 |
> get rid of ruby altogether. |
| 18 |
> |
| 19 |
> This won't suit everybody, I know, but maybe it's worth considering. |
| 20 |
|
| 21 |
What exactly does this do -- is it for a thin client or something? |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Your life is like a penny. You're going to lose it. The question is: |
| 26 |
How do |
| 27 |
you spend it? |
| 28 |
|
| 29 |
John Covici |
| 30 |
covici@××××××××××.com |
Archives