| 1 |
On Sat, 02 Sep 2017 21:33:31 +0800, Andrew Lowe wrote: |
| 2 |
|
| 3 |
> Hi all, |
| 4 |
> I'm in the process of doing a world update and due to a failed |
| 5 |
compile, |
| 6 |
> I have cause to look up through the list of stuff to compile/update. |
| 7 |
> Imagine my surprise when I saw there were three versions of Ruby wanting |
| 8 |
> to update: |
| 9 |
> |
| 10 |
> [ebuild U ] dev-lang/ruby-2.4.1-r4 [2.4.1-r3] |
| 11 |
> [ebuild U ] dev-lang/ruby-2.3.4-r4 [2.3.4-r3] |
| 12 |
> [ebuild U ] dev-lang/ruby-2.2.7-r4 [2.2.7-r3] |
| 13 |
|
| 14 |
That is unusual unless you configured this yourself. Did you set |
| 15 |
RUBY_TARGETS in make.conf? Are you on stable or testing? |
| 16 |
|
| 17 |
It would also be interesting to know what is pulling in these ruby |
| 18 |
versions. |
| 19 |
|
| 20 |
> I would prefer to get rid of Ruby, but, if memory serves me |
| 21 |
correctly, |
| 22 |
> someone associated with the kernel decided it would be a good idea to |
| 23 |
> use yet another language for something, obviously Python wasn't good |
| 24 |
> enough.... |
| 25 |
|
| 26 |
webkit-gtk and thin-provisioning-tools come to mind as pulling ruby for |
| 27 |
people that don't want it perse. |
| 28 |
|
| 29 |
Hans |
Archives