Genlop

I’ve just emerged genlop, after reading about it in a tutorial about subversion. Genlop parses portage logfiles for information, as it is said in it’s man page.

Explicitily copying it’s man page :

- Nice colorful output.
- Full Portage merge and unmerge history.
- Display date, time and build time of every merge.
- Display total and average build time of selected package[s].
- Estimate upgrade time.
- Watching current merge progress.
- Use alternate portage logfile(s).
- Match package names using regular expressions.
- Log corruption detection.

The most useful function I found is being able to know how much time did an emerge take:
The syntax is easy:

root@apple esteve [-1m] # genlop xorg-x11 -t
* x11-base/xorg-x11

Wed Jul 28 18:46:18 2004 –> x11-base/xorg-x11-6.7.0-r1
merge time: 1 hour, 11 minutes, and 57 seconds.

Tue Sep 21 19:52:37 2004 –> x11-base/xorg-x11-6.8.0-r1
merge time: 45 minutes and 58 seconds.

merged totally 2 ebuilds in 1 hour, 57 minutes, and 55 seconds.
average merge time: 58 minutes and 57 seconds.

Update:
As Pau noted in a comentary, another useful option is -i :

-i extra infos for the selected package (build specific USE and CFLAGS variables, average build time, etc)

2 Responses to “Genlop”

  1. pof says:

    One of the most useful uses of genlop I’ve found is to query the USE flags that had been used when a package was compiled, using -i:

    -i extra infos for the selected package (build specific USE and CFLAGS variables, average build time, etc)

    for example, if I want to know which USE flags i used last time I emerged apache I would do:


    s0 root # genlop -i apache
    Info about currently installed ebuild:

    * net-www/apache-2.0.49-r3
    Install date: Mon Jun 7 10:45:29 2004
    USE="berkdb gdbm threads ssl -ldap -ipv6 -doc -static"
    CFLAGS="-O3 -march=athlon-xp -pipe"

  2. Marc Vilanova Vilaser says:

    Ei! Molt

Leave a Reply