From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: texlive 2011
Date: Wed, 14 Dec 2011 17:51:27 -0800 [thread overview]
Message-ID: <CAF-1L2SJjX8fnWwzSdT6F4Vp8SRmzy78KiaFZ3b8bStqq-3d5g@mail.gmail.com> (raw)
In-Reply-To: <loom.20111214T215104-526@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Once ruby was emerged, texlive installed pretty much without any MAJOR
incident. On the #gentoo irc channel, the advice was received to unmask
ruby 1.9. There seems to be some variation in how this is done, but
that's basically all I needed to do.
On Wed, Dec 14, 2011 at 12:57 PM, james <wireless@tampabay.rr.com> wrote:
>
>
> Numerous times over the years, I have had fits with texlive*
>
> Luckily this is the first time I've installed texlive on this system.
I've installed texlive from upstream source various times, without any
major issue. It's a heck of a lot better than tetex used to be.
> Heres's m
> 1) equery b -f '/etc/texmf/.*'
> 2) Uninstalling all of the above reported ebuilds.
> 3) rm -rf /etc/texmf/*
> rm -rf /usr/share/texmf*
> emerge -C `qlist -I -C dev-texlive/*`
> 4) emerge -1 texlive
>
> Ocationally I have to rebuild the system....
> caveat emptor......
>
I did find it difficult to figure out how to install texlive on Gentoo this
time around, though. Seems a good howto is needed. This time around, I
bascially just started emerging (emerge texlive) and after all the bumps
and twists and turns, eventually I'd figured out that USE flags were
needed. I hadn't seen that at first, even though I've installed texlive
on Gentoo before, a couple or three years ago.
Alan
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2143 bytes --]
prev parent reply other threads:[~2011-12-15 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 19:35 [gentoo-user] texlive 2011 Alan E. Davis
2011-12-14 9:30 ` Willie WY Wong
2011-12-14 20:57 ` [gentoo-user] " james
2011-12-15 1:51 ` Alan E. Davis [this message]
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-1L2SJjX8fnWwzSdT6F4Vp8SRmzy78KiaFZ3b8bStqq-3d5g@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