On Tue, Dec 13, 2011 at 11:35:10AM -0800, Penguin Lover Alan E. Davis squawked:
After realizing that most packages I was installing, I used
package.keywords and ~amd64, so I went ahead and jumped---I have started
using ACCEPT_KEYWORDS for ~amd64 in /etc/make.conf . I think most of the
inconsistencies have been ironed out, but it has taken some days. One
glaring problem involves ruby. I need texlive, and I want to install
texlive 2011, and I had installed it; however, now ruby is standing in my
way.
Sorry, I am a bit confused about your description of what happened.
Can you give us a concise timeline? (Like: Day 1 installed X. Day 3,
changed keywords to ~amd64. Day 4, tried to install texlive. Got error
message Blah.)
On bugs.gentoo.org, I see some solutions, involving patches. One is a
patch for ruby (dev-lang/ruby-1.8.7_p352 ). The other is a patch for
glibc 2.14.1 .
Which bug number?
Now, unfortunately, after an emerge -avuD world, I have also run emerge
--depclean, which cleared out every package involved with texlive. I think
texlive-pictures-2011 and texlive-science-2001, possible also others, are
depending on ruby.
That, uh, should not happen. How *did* you install texlive? If you
just emerged it, it should be in the WORLD set, and should not be
removed by depclean. Also, I thought the new depclean nowadays would
refuse to run if there are unresolved conflicts?
I could also not find an accessible and up to date explanation of
installing texlive.
Set the correct USE flags (use 'equery uses texlive' or 'emerge
--pretend --verbose texlive' to see the complete list. Select the ones
you want/need). For example, on my box I have set in
'/etc/portage/package.use' the following
app-text/texlive dvi2tty extra games graphics humanities jadetex music omega
pdfannotextractor pstricks publishers science tex4ht xetex -xindy
And then just 'emerge texlive' should do the trick.
Can any one guide me towards understanding how to proceed? I would rather
not spend the next week re-installing my system. Perhaps I should back
out of ~amd64 to amd64?
Backing out of ~ is sometimes a non-trivial task, especially if it
involves downgrading system packages like glibc. When I had to do it
in the past, I had the luxury of time and so I
1) keyworded ALL currently installed version to x86 (or in your case
amd64)
2) changed the make.conf setting to x86 (amd64 in your case).
This way portage won't force you to downgrade anything that is
installed and working, and after a month or two the stable keyword
should catch up or surpass the testing keyword and you'll have a
stable system again.
W
--
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire
et vice versa ~~~ I. Newton
