From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage telling me what it's doing
Date: Sat, 2 Jun 2012 13:26:47 +0700 [thread overview]
Message-ID: <CAA2qdGUA+FEAoiP0yP=kyQLegyaqLmr7DufeYhHvDqOF3_JjiA@mail.gmail.com> (raw)
In-Reply-To: <4FC9ADE7.4040806@wht.com.au>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
On Jun 2, 2012 1:13 PM, "Andrew Lowe" <agl@wht.com.au> wrote:
>
> Hi all,
> I've just kicked off an "emerge -NuD world" and will now head out
for a while. My emerge has to do, amongst others, gcc, libreoffice, Firefox
& Thunderbird. Now when I get back I'll want to know where the emerge is up
to so, in my ignorance of portage/emerge in great depth and with only
compiler output spewing up the screen, I'll fire up another terminal, and
now don't laugh, I'll do "emerge --pretend -NuD world". That will tell me
what's currently being compiled as it will be the top thingy on the list.
There has to be a better way....
>
> Is there a way so that the terminal that the emerge is happening
in can display additional info? At the moment, I get:
>
> /home/agl: emerge
>
> can I get, say:
>
> /home/agl: emerge www-client/firefox
>
> by setting some config variable? Failing that is there a log file that
lists just what's been emerged, not a whole lot of "checking this, checking
that, compiling this file, linking that library, whoops, error here..."
sort of thing.
>
> Any thoughts, greatly appreciated,
>
I never tried it while an emerge @world us running, but elogv/elogviewer
sorts by last emerge time.
Thus, the last package emerged -- successfully or not -- is topmost.
Rgds,
[-- Attachment #2: Type: text/html, Size: 1606 bytes --]
next prev parent reply other threads:[~2012-06-02 6:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 6:08 [gentoo-user] Portage telling me what it's doing Andrew Lowe
2012-06-02 6:26 ` Pandu Poluan [this message]
2012-06-02 6:44 ` Walter Dnes
2012-06-03 14:54 ` YoYo Siska
2012-06-03 18:01 ` Andrew Lowe
2012-06-02 6:59 ` Hinnerk van Bruinehsen
2012-06-02 7:06 ` Dale
2012-06-05 7:46 ` Bryan Gardiner
2012-06-05 11:43 ` Dale
2012-06-05 14:41 ` Kerwin Hui
2012-06-05 16:37 ` Bryan Gardiner
2012-06-05 18:53 ` Neil Bothwick
2012-06-05 22:54 ` Dale
2012-06-06 0:05 ` Neil Bothwick
2012-06-06 0:17 ` Dale
2012-06-02 8:41 ` Alex Schuster
2012-06-03 0:05 ` David Relson
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='CAA2qdGUA+FEAoiP0yP=kyQLegyaqLmr7DufeYhHvDqOF3_JjiA@mail.gmail.com' \
--to=pandu@poluan.info \
--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