1 |
After realizing that most packages I was installing, I used |
2 |
package.keywords and ~amd64, so I went ahead and jumped---I have started |
3 |
using ACCEPT_KEYWORDS for ~amd64 in /etc/make.conf . I think most of the |
4 |
inconsistencies have been ironed out, but it has taken some days. One |
5 |
glaring problem involves ruby. I need texlive, and I want to install |
6 |
texlive 2011, and I had installed it; however, now ruby is standing in my |
7 |
way. |
8 |
|
9 |
On bugs.gentoo.org, I see some solutions, involving patches. One is a |
10 |
patch for ruby (dev-lang/ruby-1.8.7_p352 ). The other is a patch for |
11 |
glibc 2.14.1 . |
12 |
|
13 |
I'm not sure how to handle this, but I'm pretty sure I don't want to mess |
14 |
around with a personal overlay of glibc. |
15 |
|
16 |
Now, unfortunately, after an emerge -avuD world, I have also run emerge |
17 |
--depclean, which cleared out every package involved with texlive. I think |
18 |
texlive-pictures-2011 and texlive-science-2001, possible also others, are |
19 |
depending on ruby. |
20 |
|
21 |
I could also not find an accessible and up to date explanation of |
22 |
installing texlive. |
23 |
|
24 |
Can any one guide me towards understanding how to proceed? I would rather |
25 |
not spend the next week re-installing my system. Perhaps I should back |
26 |
out of ~amd64 to amd64? |
27 |
|
28 |
Thanks, |
29 |
|
30 |
Alan Davis |