Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Suggestions for a couple handy portage commands
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo Chat
View previous topic :: View next topic  
Author Message
ExecutorElassus
l33t
l33t


Joined: 11 Mar 2004
Posts: 742
Location: Stuttgart, Germany

PostPosted: Thu Oct 25, 2012 10:11 am    Post subject: Suggestions for a couple handy portage commands Reply with quote

So, I run into this problem a lot, and I'd like to put in a friendly request for portage (or equery?) to have a feature added to return the following information:

list of all package atoms updated/changed by emerge since [date]
last date [package atom] was updated/changed by emerge
"last date updated/changed" for dependencies returned by 'equery depgraph [package atom]'

See, I often run 'emerge -uD world' several times a week, and then discover that some random package isn't working. It's often a dependency that has broken (either at compile- or run-time), but I don't know which packages have been most recently updated. This would spare me getting the answer "just downgrade everything until the package works again" when I ask about it on the forum, and would help narrow down bug tracking as well. If I know a package worked last week, but not today, then I can be pretty safe in assuming that the problem lies only in packages that have been changed in between (obviously not always, but usually).

I suppose this would mean time-stamping emerge operations, but that might not be too difficult to implement?

Cheers,

EE
(who knows jack diddly about programming or anything, so is obviously being a dilettante)
Back to top
View user's profile Send private message
baaann
Guru
Guru


Joined: 23 Jan 2006
Posts: 490
Location: uk

PostPosted: Thu Oct 25, 2012 11:27 am    Post subject: Reply with quote

If you haven't set it up already then I recommend elog and its command line viewer elogv.

You set up elog in make.conf, see
Code:
less /usr/share/portage/config/make.conf.example
and

http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=1

then
Code:
emerge -av elogv


In addition eix is an excellent utility and includes date operations. It's functions are too numerous to list here
Code:
emerge -av eix
and read the man page
Back to top
View user's profile Send private message
dol-sen
Developer
Developer


Joined: 30 Jun 2002
Posts: 2521
Location: Richmond, BC, Canada

PostPosted: Thu Oct 25, 2012 2:49 pm    Post subject: Reply with quote

First off, emerge does timestamp all merges, so that information is readily available, albiet, not easily human readable. You could however look at the modified date if you manually look through the /var/db/pkg/{cat}/{pkg-ver} entries.

Quote:
list of all package atoms updated/changed by emerge since [date]

I created enalyze in gentoolkit for full installed pkg db analysis. So, I could add that report to it.

Quote:
last date [package atom] was updated/changed by emerge
"last date updated/changed" for dependencies returned by 'equery depgraph [package atom]'

Yes it would be possible to add a new equery sub-module to show the time a pkg was last merged, or add that info to an existing one.
It should also be possible to add the merge time to the equery depgragh display.
One of the things we are intending is to add custom formatting output to all equery sub-modules, so if that information is made available, it could be specified in the output. Custom formatting is available in some modules currently, but the time info is not made available yet.

Please file a feature request "Enhancement" bug in bugzilla for these. We are starting to plan changes for gentoolkit-0.3.1
That way they won't be forgotten about.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...
Back to top
View user's profile Send private message
khayyam
Advocate
Advocate


Joined: 07 Jun 2012
Posts: 2184

PostPosted: Fri Oct 26, 2012 5:40 pm    Post subject: Re: Suggestions for a couple handy portage commands Reply with quote

ExecutorElassus wrote:
list of all package atoms updated/changed by emerge since [date]

ExecutorElassus ... 'date' is not always staightforward as there are many date formats, 2012-10-26, 26-10-12, 10-26-12, 10-26, Oct 26, 20121026, 26102012, etc, but a dated list of updates/changes can currently be aquired via 'qlop -lu' (app-portage/portage-utils), and there are methods of parsing the data provided, ie, for 'two days ago':

Code:
% qlop -Cl | awk -v days="-2" -F '>>>[[:space:]]*' '{split($0,a,/[[:space:]]+/)} strftime("%a %b %d",systime()+(days*86400)) == a[1]" "a[2]" "a[3] {print $2}'

Doing something similar 'from date to current date' is possible, but the date format used would make it somewhat compilcated (at least for a oneliner). As dol-sen noted this information is availble in /var/db/pkg/ (qlop queries /varr/log/emerge.log I believe) so using this data would probably be a better solution.

ExecutorElassus wrote:
last date [package atom] was updated/changed by emerge

'eix' (app-portage/eix) provides this information in the 'Installed versions:' field.

ExecutorElassus wrote:
"last date updated/changed" for dependencies returned by 'equery depgraph [package atom]'

Hmmm ... but depgraph lists dependencies (ie: based on 'use') whether these are installed or not, but ok, some clue as to installed/uninstalled deps might be useful.

ExecutorElassus wrote:
See, I often run 'emerge -uD world' several times a week, and then discover that some random package isn't working. It's often a dependency that has broken (either at compile- or run-time), but I don't know which packages have been most recently updated. This would spare me getting the answer "just downgrade everything until the package works again" when I ask about it on the forum, and would help narrow down bug tracking as well. If I know a package worked last week, but not today, then I can be pretty safe in assuming that the problem lies only in packages that have been changed in between (obviously not always, but usually).

Well, besides 'qlop -lu' you might want to read the section on PORTAGE_ELOG* in /usr/share/portage/config/make.conf.example.

best ... khay
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31713
Location: 56N 3W

PostPosted: Fri Oct 26, 2012 6:25 pm    Post subject: Reply with quote

ExecutorElassus,

look at genlop, it does some of the things you want.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
djdunn
l33t
l33t


Joined: 26 Dec 2004
Posts: 688
Location: Arrakis

PostPosted: Fri Oct 26, 2012 8:13 pm    Post subject: Reply with quote

eix and eix-sync shows you all the updates to the tree since last sync
_________________
"Yesterday is history, tomorrow is a mystery, but today is a gift. That is why it is called the present."

-Master Oogway
Back to top
View user's profile Send private message
geeksheik
n00b
n00b


Joined: 07 Sep 2003
Posts: 68

PostPosted: Fri Oct 26, 2012 10:44 pm    Post subject: Reply with quote

ExecutorElassus,

You ask a question about queries that I seem to do about a dozen times per day for more years than I'd like to admit.

In order to cope with this insane amount of repetition, I've concocted a handful of script and aliases (a shorthand of sorts) as a survival mechanism. I'm certainly not the only one who's come up with a custom set (or framework) of utilities for Gentoo/Linux/Unix sysadmin, but this seems like a fine opportunity to post mine.
Note: I have not yet looked into elogv (thanks for the tip, @baaann); just merged it. I only hope that I don't regret posting my primitive methods of operation after trying it out...

So, here's what I do:

In general, I make use of /var/log/emerge.log for this information. ...but as you've probably seen, the time stamps are relatively-ugly and not-very-human-readable.

Quote:
1351284132: Started emerge on: Oct 26, 2012 22:42:11
1351284132: *** emerge --ask --verbose elogv
1351284143: >>> emerge (1 of 1) app-portage/elogv-0.7.4 to /
1351284143: === (1 of 1) Cleaning (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
1351284144: === (1 of 1) Compiling/Merging (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
1351284149: === (1 of 1) Merging (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
1351284150: >>> AUTOCLEAN: app-portage/elogv:0
1351284152: === (1 of 1) Updating world file (app-portage/elogv-0.7.4)
1351284152: === (1 of 1) Post-Build Cleaning (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
1351284152: ::: completed emerge (1 of 1) app-portage/elogv-0.7.4 to /
1351284152: *** Finished. Cleaning up...
1351284154: *** exiting successfully.
1351284154: *** terminating.


Step #1: convert timestamps to human-readable:

The date format is in epochs (seconds since 1/1/70). Converting it to human-readable is most-conveniently done in a stream; pipe the log file in and the results out to filter, a file, less, tee, whatever...

This could be a script or an alias; let's call it format-epochs.sh:
Code:
while read 'line' ; do echo "`date -d "1970-1-1 ${line/:*/} sec UTC" "+%Y-%m-%d %H:%M:%S"`:${line#*:}" ; done


like:
Code:
alias format-epochs='while read 'line' ; do echo "`date -d "1970-1-1 ${line/:*/} sec UTC" "+%Y-%m-%d %H:%M:%S"`:${line#*:}" ; done'

or in a file:
Code:
$!/bin/bash
while read 'line' ; do echo "`date -d "1970-1-1 ${line/:*/} sec UTC" "+%Y-%m-%d %H:%M:%S"`:${line#*:}" ; done



Use it like this:

Code:
tail -n 100 /var/log/emerge.log | format-epochs | less


It will give you a list of the 100 most-recent emerge log entries, nicely-formatted timestamps prefixing each line.

Example output (clipped a bit):

Quote:

2012-10-22 19:58:55: *** Finished. Cleaning up...
2012-10-22 19:58:57: *** exiting successfully.
2012-10-22 19:58:57: *** terminating.
2012-10-26 22:42:12: Started emerge on: Oct 26, 2012 22:42:11
2012-10-26 22:42:12: *** emerge --ask --verbose elogv
2012-10-26 22:42:23: >>> emerge (1 of 1) app-portage/elogv-0.7.4 to /
2012-10-26 22:42:23: === (1 of 1) Cleaning (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
2012-10-26 22:42:24: === (1 of 1) Compiling/Merging (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
2012-10-26 22:42:29: === (1 of 1) Merging (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
2012-10-26 22:42:30: >>> AUTOCLEAN: app-portage/elogv:0
2012-10-26 22:42:32: === (1 of 1) Updating world file (app-portage/elogv-0.7.4)
2012-10-26 22:42:32: === (1 of 1) Post-Build Cleaning (app-portage/elogv-0.7.4::/usr/portage/app-portage/elogv/elogv-0.7.4.ebuild)
2012-10-26 22:42:32: ::: completed emerge (1 of 1) app-portage/elogv-0.7.4 to /
2012-10-26 22:42:32: *** Finished. Cleaning up...
2012-10-26 22:42:34: *** exiting successfully.
2012-10-26 22:42:34: *** terminating.


Next step: there's a near-infinite number of ways that you can filter the output. For instances, look only at packages that have been successfully-installed:

Code:
cat /var/log/emerge.log | grep "completed emerge" |  format-epochs | less


...or look only at operations that were done after a certain date/time:

Code:
tail -n 100 /var/log/emerge.log | format-epochs | while read line ; do [[ "$line" > "2012-10-22 01:37:33" ]] && echo "$line" ; done


...or combine the two filters to answer your first original question:

> list of all package atoms updated/changed by emerge since [date]

Code:
tail -n 100 /var/log/emerge.log | grep "completed emerge" | format-epochs | while read line ; do [[ "$line" > "2012-10-22 01:37:33" ]] && echo "$line" ; done


Quote:
2012-10-22 01:37:33: ::: completed emerge (1 of 3) sys-apps/v86d-0.1.10 to /
2012-10-22 01:37:51: ::: completed emerge (2 of 3) app-emulation/virtualbox-modules-4.1.22 to /
2012-10-22 01:38:20: ::: completed emerge (3 of 3) x11-drivers/nvidia-drivers-295.75 to /
2012-10-22 19:58:55: ::: completed emerge (1 of 1) app-text/acroread-9.5.1-r1 to /
2012-10-26 22:42:32: ::: completed emerge (1 of 1) app-portage/elogv-0.7.4 to /


As a side note, I often use format-epochs.sh while watching background emerge processes. I made the following alias for this:

Code:
alias tailemerge='tail -f /var/log/emerge.log | format-epochs'

Run this in a shell window to get updates on how your (nice) emerge tasks are coming along. You'll find this useful if you ever re-visit a machine that hasn't been updated in a long time...

Quote:
-> tailemerge
2012-10-26 23:24:26: === (4 of 12) Compiling/Merging (app-emulation/virt-manager-0.9.4::/usr/portage/app-emulation/virt-manager/virt-manager-0.9.4.ebuild)
2012-10-26 23:24:34: === (4 of 12) Merging (app-emulation/virt-manager-0.9.4::/usr/portage/app-emulation/virt-manager/virt-manager-0.9.4.ebuild)
2012-10-26 23:24:35: >>> AUTOCLEAN: app-emulation/virt-manager:0
2012-10-26 23:24:35: === Unmerging... (app-emulation/virt-manager-0.9.1)
2012-10-26 23:24:43: >>> unmerge success: app-emulation/virt-manager-0.9.1
2012-10-26 23:24:45: === (4 of 12) Post-Build Cleaning (app-emulation/virt-manager-0.9.4::/usr/portage/app-emulation/virt-manager/virt-manager-0.9.4.ebuild)
2012-10-26 23:24:45: ::: completed emerge (4 of 12) app-emulation/virt-manager-0.9.4 to /
2012-10-26 23:24:46: >>> emerge (5 of 12) www-plugins/gnash-0.8.10_p20120903 to /
2012-10-26 23:24:46: === (5 of 12) Cleaning (www-plugins/gnash-0.8.10_p20120903::/usr/portage/www-plugins/gnash/gnash-0.8.10_p20120903.ebuild)
2012-10-26 23:24:46: === (5 of 12) Compiling/Merging (www-plugins/gnash-0.8.10_p20120903::/usr/portage/www-plugins/gnash/gnash-0.8.10_p20120903.ebuild)



...or if you want to see a history of build performance, take a look at the history of complile times for whatever package you're interested in. Just grep for the start-of-compile and end-of-compile keywords in the log file (both coincidentally contain the string "Merging" with a trailing space:

Code:
cat /var/log/emerge.log | grep www-client/chromium | grep "Merging " | format-epochs | less

Quote:
2012-09-09 12:53:32: === (95 of 363) Compiling/Merging (www-client/chromium-21.0.1180.89::/usr/portage/www-client/chromium/chromium-21.0.1180.89.ebuild)
2012-09-09 13:31:11: === (95 of 363) Merging (www-client/chromium-21.0.1180.89::/usr/portage/www-client/chromium/chromium-21.0.1180.89.ebuild)
2012-10-04 17:12:28: === (25 of 26) Compiling/Merging (www-client/chromium-22.0.1229.79::/usr/portage/www-client/chromium/chromium-22.0.1229.79.ebuild)
2012-10-04 17:44:23: === (25 of 26) Merging (www-client/chromium-22.0.1229.79::/usr/portage/www-client/chromium/chromium-22.0.1229.79.ebuild)
2012-10-14 20:59:05: === (67 of 74) Compiling/Merging (www-client/chromium-22.0.1229.94::/usr/portage/www-client/chromium/chromium-22.0.1229.94.ebuild)
2012-10-14 21:36:26: === (67 of 74) Merging (www-client/chromium-22.0.1229.94::/usr/portage/www-client/chromium/chromium-22.0.1229.94.ebuild)


...which brings us kind of around to your second question:

> last date [package atom] was updated/changed by emerge

Just use the above query, but only look at the last line:

Code:
cat /var/log/emerge.log | grep www-client/chromium | grep "Merging " | format-epochs | tail -n 1

Quote:
2012-10-14 21:36:26: === (67 of 74) Merging (www-client/chromium-22.0.1229.94::/usr/portage/www-client/chromium/chromium-22.0.1229.94.ebuild)


...as for the last question, I'm rarely querying all outputs of a depgraph in one fell swoop. However, for reasons I cannot explain, I took a minute or two to slap something together. I can't vouch for its accuracy; just take it as a suggestion for a possible starting point. (WARNING: really ugly. Parental discretion is advised.)

> "last date updated/changed" for dependencies returned by 'equery depgraph [package atom]'

Code:
equery depgraph chromium | while read line ; do [[ ! "${line#*:}" ]] && continue ; pkg="${line#*]}" ; echo $pkg ; done | sort | uniq | while read line ; do cat /var/log/emerge.log | grep "$line" | grep "Merging " | format-epochs | tail -n 1 ; done


Quote:
2011-10-23 13:39:54: === (1 of 181) Merging (app-arch/bzip2-1.0.6-r3::/usr/portage/app-arch/bzip2/bzip2-1.0.6-r3.ebuild)
2012-10-04 17:03:15: === (19 of 26) Merging (dev-lang/nacl-toolchain-newlib-0_p9093::/usr/portage/dev-lang/nacl-toolchain-newlib/nacl-toolchain-newlib-0_p9093.ebuild)
2011-10-23 14:15:55: === (36 of 181) Merging (dev-lang/perl-5.12.4-r1::/usr/portage/dev-lang/perl/perl-5.12.4-r1.ebuild)
2012-05-24 01:09:02: === (28 of 281) Merging (dev-lang/python-2.6.8::/usr/portage/dev-lang/python/python-2.6.8.ebuild)
2012-06-23 16:06:25: === (113 of 195) Merging (dev-lang/python-2.7.3-r2::/usr/portage/dev-lang/python/python-2.7.3-r2.ebuild)
2012-10-14 20:20:03: === (18 of 74) Merging (dev-lang/v8-3.12.19.15::/usr/portage/dev-lang/v8/v8-3.12.19.15.ebuild)
2012-01-15 14:07:11: === (22 of 31) Merging (dev-lang/yasm-1.2.0::/usr/portage/dev-lang/yasm/yasm-1.2.0.ebuild)
2012-07-30 23:42:59: === (15 of 63) Merging (dev-libs/dbus-glib-0.100::/usr/portage/dev-libs/dbus-glib/dbus-glib-0.100.ebuild)
2011-10-23 13:57:57: === (27 of 181) Merging (dev-libs/elfutils-0.149::/usr/portage/dev-libs/elfutils/elfutils-0.149.ebuild)
2012-10-14 20:14:29: === (1 of 74) Merging (dev-libs/expat-2.1.0-r2::/usr/portage/dev-libs/expat/expat-2.1.0-r2.ebuild)
2012-09-06 11:28:33: === (2 of 102) Merging (dev-libs/icu-49.1.2::/usr/portage/dev-libs/icu/icu-49.1.2.ebuild)
2012-07-30 08:07:06: === (4 of 63) Merging (dev-libs/libevent-2.0.19::/usr/portage/dev-libs/libevent/libevent-2.0.19.ebuild)
2012-06-26 21:36:57: === (4 of 9) Merging (dev-libs/libgcrypt-1.5.0-r2::/usr/portage/dev-libs/libgcrypt/libgcrypt-1.5.0-r2.ebuild)
2012-09-20 13:32:34: === (9 of 38) Merging (dev-libs/libxml2-2.8.0-r2::/usr/portage/dev-libs/libxml2/libxml2-2.8.0-r2.ebuild)
2012-10-04 16:41:04: === (10 of 26) Merging (dev-libs/libxslt-1.1.27::/usr/portage/dev-libs/libxslt/libxslt-1.1.27.ebuild)
2012-09-11 22:02:57: === (7 of 263) Merging (dev-libs/nss-3.13.6::/usr/portage/dev-libs/nss/nss-3.13.6.ebuild)
2012-09-12 08:14:59: === (11 of 39) Merging (dev-python/ply-3.4::/usr/portage/dev-python/ply/ply-3.4.ebuild)
2012-10-04 16:42:33: === (12 of 26) Merging (dev-python/simplejson-2.6.0::/usr/portage/dev-python/simplejson/simplejson-2.6.0.ebuild)
2010-09-01 09:40:01: === (40 of 365) Merging (dev-util/gperf-3.0.4::/usr/portage/dev-util/gperf/gperf-3.0.4.ebuild)
2011-10-23 15:29:47: === (134 of 181) Merging (dev-vcs/subversion-1.6.17-r7::/usr/portage/dev-vcs/subversion/subversion-1.6.17-r7.ebuild)
2011-10-23 14:54:19: === (114 of 181) Merging (gnome-base/gconf-2.32.4::/usr/portage/gnome-base/gconf/gconf-2.32.4.ebuild)
2011-10-23 15:02:47: === (124 of 181) Merging (gnome-base/gnome-keyring-2.32.1-r1::/usr/portage/gnome-base/gnome-keyring/gnome-keyring-2.32.1-r1.ebuild)
2012-03-18 22:27:17: === (15 of 30) Merging (media-libs/alsa-lib-1.0.25-r1::/usr/portage/media-libs/alsa-lib/alsa-lib-1.0.25-r1.ebuild)
2010-10-03 21:22:22: === (3 of 5) Merging (media-libs/flac-1.2.1-r3::/usr/portage/media-libs/flac/flac-1.2.1-r3.ebuild)
2012-08-02 22:45:01: === (2 of 17) Merging (media-libs/libjpeg-turbo-1.2.1::/usr/portage/media-libs/libjpeg-turbo/libjpeg-turbo-1.2.1.ebuild)
2012-10-14 20:14:53: === (3 of 74) Merging (media-libs/libpng-1.5.13-r1::/usr/portage/media-libs/libpng/libpng-1.5.13-r1.ebuild)
2012-09-09 12:35:09: === (72 of 363) Merging (media-libs/libwebp-0.2.0::/usr/portage/media-libs/libwebp/libwebp-0.2.0.ebuild)
2010-09-01 01:30:03: === (304 of 1091) Merging (media-libs/speex-1.2_rc1::/usr/portage/media-libs/speex/speex-1.2_rc1.ebuild)
2012-03-24 01:33:06: === (6 of 15) Merging (media-sound/pulseaudio-1.1-r1::/usr/portage/media-sound/pulseaudio/pulseaudio-1.1-r1.ebuild)
2012-09-09 11:47:29: === (12 of 363) Merging (net-misc/rsync-3.0.9-r2::/usr/portage/net-misc/rsync/rsync-3.0.9-r2.ebuild)
2012-05-17 20:55:59: === (21 of 67) Merging (net-print/cups-1.5.2-r4::/usr/portage/net-print/cups/cups-1.5.2-r4.ebuild)
2012-10-14 20:22:55: === (22 of 74) Merging (sys-apps/dbus-1.6.8::/usr/portage/sys-apps/dbus/dbus-1.6.8.ebuild)
2012-08-05 17:24:52: === (1 of 21) Merging (sys-apps/sed-4.2.1-r1::/usr/portage/sys-apps/sed/sed-4.2.1-r1.ebuild)
2011-07-02 19:37:29: === (56 of 346) Merging (sys-devel/bison-2.4.3::/usr/portage/sys-devel/bison/bison-2.4.3.ebuild)
2011-09-29 15:38:11: === (8 of 42) Merging (sys-devel/flex-2.5.35_p10::/usr/portage/sys-devel/flex/flex-2.5.35_p10.ebuild)
2012-09-09 11:57:45: === (46 of 363) Merging (sys-devel/make-3.82-r3::/usr/portage/sys-devel/make/make-3.82-r3.ebuild)
2012-10-22 01:20:23: === (3 of 17) Merging (sys-fs/udev-171-r8::/usr/portage/sys-fs/udev/udev-171-r8.ebuild)
2011-01-06 16:16:38: === (6 of 220) Merging (virtual/libusb-1::/usr/portage/virtual/libusb/libusb-1.ebuild)
2012-05-15 20:48:11: === (12 of 91) Merging (virtual/pkgconfig-0::/usr/portage/virtual/pkgconfig/pkgconfig-0.ebuild)
2010-09-01 01:14:39: === (208 of 1091) Merging (virtual/ttf-fonts-1::/usr/portage/virtual/ttf-fonts/ttf-fonts-1.ebuild)
2012-10-14 21:36:26: === (67 of 74) Merging (www-client/chromium-22.0.1229.94::/usr/portage/www-client/chromium/chromium-22.0.1229.94.ebuild)
2012-06-23 16:03:20: === (100 of 195) Merging (x11-apps/xhost-1.0.5::/usr/portage/x11-apps/xhost/xhost-1.0.5.ebuild)
2012-06-23 16:45:39: === (133 of 195) Merging (x11-base/xorg-server-1.12.2::/usr/portage/x11-base/xorg-server/xorg-server-1.12.2.ebuild)
2012-10-14 20:38:54: === (41 of 74) Merging (x11-libs/gtk+-2.24.12::/usr/portage/x11-libs/gtk+/gtk+-2.24.12.ebuild)
2012-06-23 16:00:50: === (85 of 195) Merging (x11-libs/libXScrnSaver-1.2.2::/usr/portage/x11-libs/libXScrnSaver/libXScrnSaver-1.2.2.ebuild)
2012-06-23 16:00:41: === (84 of 195) Merging (x11-libs/libXinerama-1.1.2::/usr/portage/x11-libs/libXinerama/libXinerama-1.1.2.ebuild)
2012-06-23 16:02:20: === (94 of 195) Merging (x11-libs/libXtst-1.2.1::/usr/portage/x11-libs/libXtst/libXtst-1.2.1.ebuild)
2012-05-17 20:51:30: === (17 of 67) Merging (x11-misc/xdg-utils-1.1.0_rc1_p20120319::/usr/portage/x11-misc/xdg-utils/xdg-utils-1.1.0_rc1_p20120319.ebuild)

I hope somebody out there finds this excessively-long-winded post useful at some point.


Last edited by geeksheik on Sun Nov 11, 2012 2:39 pm; edited 1 time in total
Back to top
View user's profile Send private message
geeksheik
n00b
n00b


Joined: 07 Sep 2003
Posts: 68

PostPosted: Sun Nov 11, 2012 2:35 pm    Post subject: Reply with quote

It looks like both genlop and qlop do most, if not all, of what you're looking for. Ignore my lengthy manifesto, unless you're looking for a home-rolled solution.

elogv requires some customization make.conf, which I didn't bother with.
Back to top
View user's profile Send private message
ExecutorElassus
l33t
l33t


Joined: 11 Mar 2004
Posts: 742
Location: Stuttgart, Germany

PostPosted: Thu Nov 15, 2012 8:04 pm    Post subject: Reply with quote

holy crap, the forum didn't notify me of any of these replies. Thanks, y'all!

I'll dig through the text when I have some free time, and see what I can work out. I'll start with the stock solutions like genlop and qlop, and see about rolling some custom stuff later.

Cheers,

EE
Back to top
View user's profile Send private message
ppurka
Advocate
Advocate


Joined: 26 Dec 2004
Posts: 3205

PostPosted: Thu Nov 15, 2012 9:59 pm    Post subject: Reply with quote

ExecutorElassus wrote:
holy crap, the forum didn't notify me of any of these replies. Thanks, y'all!
You are right. I am not getting any emails either on watched topics.
_________________
emerge --quiet redefined | E17 vids: I, II
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Chat All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum