> On Tue, 05 Jun 2012 06:43:30 -0500
> Dale <rdalek1...@gmail.com> wrote:
>
> > If it is updates, I do this:
> >
> > emerge --resume -p | genlop -p
> >
Fantastic, thanks, --resume has always seemed like black magic to me
(to the point where I do big installs by editing
/var/lib/portage/world and emerging world in case something breaks),
but it seems simpler than I had thought.
> > That tells what is left time wise and is faster to since it is working
> > off the list already made. Then again, it seems genlop wasn't working
> > right the other day. I meant to check into that but forgot about it.
> > It seems, if I recall correctly, that if a package has not been compiled
> > before, it just spits out a error message. It used to spit out that
> > there was 'no info available for package foo' then just show the rest.
> > Now, it just pukes on the keyboard and dies.
> >
> > Progress. It always breaks things. < sighs >
Hmm, the behaviour for me has always seemed to be: don't count
packages that haven't been emerged previously, and if the last package
emerge spits out is unknown to genlop, then abort and don't print an
estimate. Really annoying.
On Tue, 5 Jun 2012 22:41:26 +0800
Kerwin Hui <kwk...@hkbn.net> wrote:
> Any reason why genlop instead of qlop (app-portage/portage-utils)?
>
> IIRC once upon a time there was a change of portage log output and
> genlop failed me but qlop didn't. I changed to qlop and never looked
> back.
>
> Kerwin.
qlop's great too, and much faster. I've seen slight (tens of seconds)
discrepancies between the build times given by genlop and qlop during
a build, and on occasion have seen qlop reset its counter weirdly,
though maybe this happened in the install phase:
$ qlop -c
* mail-client/evolution-2.30.2-r1
started: Sat Sep 25 15:38:23 2010
elapsed: 15 minutes, 54 seconds
chroot: /
$ genlop -c
Currently merging 59 out of 76
* mail-client/evolution-2.30.2-r1
current merge time: 1 hour, 21 minutes and 36 seconds.
ETA: unknown.
In any case, that was a while ago :).
Cheers,
Bryan
