From: elmar bucher <elmbeech@gmail.com>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] gentoo and yeeloong mips and latex
Date: Mon, 26 Nov 2012 21:11:49 +0200 [thread overview]
Message-ID: <CA+_9G+_vwoHx6Gzxjjk=oJsqRM9fBEWDGBq=ccNJ6OSUmtqNuA@mail.gmail.com> (raw)
In-Reply-To: <20121126085410.GA31254@earth.members.linode.com>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Dear Christopoulos,
It was really a noob question ...
But now I'm back on track.
Thank you!
Have a good day, Elmar
On 26 November 2012 10:54, Panagiotis Christopoulos <pchrist@gentoo.org>wrote:
> On 17:54 Sun 25 Nov , elmar bucher wrote:
> > dear Gentoo Mips list,
> >
> > I successfully installed gentoo on a yeeloong (with stage 4 tar ball and
> > hardened flavour) as described here:
> > http://www.gentoo.org/proj/en/base/mips/yeeloong.xml
> >
> > I successfully updated the portage tree.
> >
> > Now I would like to get latex running.
> > but
> > emerge search tetex
> > find nothing.
> >
> > any hint how to step further into this adventure?
>
> Try "emerge -pv texlive" . Don't know if there are mips keywords for all
> dependencies, but probably there are.
>
> If you're new to gentoo, you may want to read [1] and [2].
>
> However, as gentoo-mips is a mailing list only for discussions regarding
> gentoo's MIPS project, if you need user support, you can try
> gentoo-user (which has more activity).
>
> For mips related questions, of course you're welcome to post here.
>
> [1] http://www.gentoo.org/doc/en/handbook/handbook-mips.xml
> [2] http://www.gentoo.org/doc/en/handbook/handbook-mips.xml?part=2&chap=1
>
> --
> Panagiotis Christopoulos ( pchrist )
> ( Gentoo Lisp Project )
>
[-- Attachment #2: Type: text/html, Size: 2179 bytes --]
prev parent reply other threads:[~2012-11-26 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 15:54 [gentoo-mips] gentoo and yeeloong mips and latex elmar bucher
2012-11-26 8:54 ` Panagiotis Christopoulos
2012-11-26 19:11 ` elmar bucher [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='CA+_9G+_vwoHx6Gzxjjk=oJsqRM9fBEWDGBq=ccNJ6OSUmtqNuA@mail.gmail.com' \
--to=elmbeech@gmail.com \
--cc=gentoo-mips@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