From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage GUI interfaces...
Date: Wed, 24 Feb 2010 23:20:31 -0600 [thread overview]
Message-ID: <4B86089F.3050303@gmail.com> (raw)
In-Reply-To: <4B85EAFE.1040303@gmail.com>
chrome://messenger/locale/messengercompose/composeMsgs.properties:
> BRM wrote:
>
>> I am interested in finding a GUI interface for working with portage, preferably for KDE4.
>> Namely b/c I am getting a little tired of having konsole windows open and not being able to keep track of where I am in the emerge update process - something a GUI _ought_ to be able to resolve.
>>
>> In googling, I noticed Kuroo, but it's no longer maintained (nearly 2 years out of date now, so it would have to have been KDE3) so it's been understandably removed from mainline portage - though I also noticed information on a Kuroo overlay.
>>
>> And I also came across Porthole; however, all versions are marked Unstable/Testing (~) at the moment.
>>
>> Can anyone give some advice on these or others?
>>
>>
>> Ben
>>
>>
>>
>>
>>
> In the case that there is not a GUI tool, why not run as root # tail -f
> /var/log/emerge.log
>
> It tells you what is being installed at present
>
> Another, to see what you are downloading is # tail -f
> /var/log/emerge-fetch.log
>
> Good Luck :)
>
>
Another good tool is genlop. Just type in genlop -c and it will tell
you what is emerging, what number the package is and the estimated times
as well. What number the package is looks something like this:
emerging #4 of 8 packages. That tells you it is on package 4 out of 8
that will be emerged. The estimated time only works if the package has
been emerged at least once before.
Sorry, it is command line. It appears you have already discovered about
everything else. lol
Dale
:-) :-)
next prev parent reply other threads:[~2010-02-25 6:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 2:40 [gentoo-user] Portage GUI interfaces BRM
2010-02-25 3:11 ` Zeerak Mustafa Waseem
2010-02-25 3:14 ` ubiquitous1980
2010-02-25 5:20 ` Dale [this message]
2010-02-25 7:19 ` Alan McKinnon
2010-02-25 14:32 ` BRM
2010-02-25 3:17 ` ubiquitous1980
2010-02-25 5:24 ` Dale
2010-02-25 5:32 ` Ronan Arraes Jardim Chagas
2010-02-25 6:35 ` Stroller
2010-02-25 14:03 ` Ronan Arraes Jardim Chagas
2010-02-25 14:40 ` [gentoo-user] Error in emerge git Konstantinos Bekiaris
2010-02-25 14:51 ` Xavier Parizet
2010-02-25 7:43 ` [gentoo-user] Portage GUI interfaces daid kahl
2010-02-25 19:35 ` Dale
2010-02-25 9:44 ` Stefano Crocco
2010-02-25 15:32 ` Peter Humphrey
2010-02-25 19:40 ` Dale
2010-02-26 11:59 ` Peter Humphrey
2010-02-26 12:17 ` Neil Bothwick
2010-02-26 14:39 ` Peter Humphrey
2010-02-26 15:08 ` J. Roeleveld
2010-02-26 17:34 ` Peter Humphrey
2010-02-27 3:52 ` Mark David Dumlao
2010-02-27 11:01 ` Neil Bothwick
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=4B86089F.3050303@gmail.com \
--to=rdalek1967@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