From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] texlive 2011
Date: Tue, 13 Dec 2011 11:35:10 -0800 [thread overview]
Message-ID: <CAF-1L2S-3T5q-CC7kDT7aCwT+pGmZL92vx9a8VtosvB48P2www@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
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.
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 .
I'm not sure how to handle this, but I'm pretty sure I don't want to mess
around with a personal overlay of glibc.
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.
I could also not find an accessible and up to date explanation of
installing texlive.
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?
Thanks,
Alan Davis
[-- Attachment #2: Type: text/html, Size: 1356 bytes --]
next reply other threads:[~2011-12-13 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 19:35 Alan E. Davis [this message]
2011-12-14 9:30 ` [gentoo-user] texlive 2011 Willie WY Wong
2011-12-14 20:57 ` [gentoo-user] " james
2011-12-15 1:51 ` Alan E. Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF-1L2S-3T5q-CC7kDT7aCwT+pGmZL92vx9a8VtosvB48P2www@mail.gmail.com \
--to=lngndvs@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox