From: Roman Gaufman <hackeron@gmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Ability to display notices/warnings after emerge (+script).
Date: Sat, 16 Oct 2004 23:42:06 +0000 [thread overview]
Message-ID: <921ad39e041016164269135cfa@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
Very messy piece of code, but works none the less to let you display
all meaningful messages after emerge.
It will get parse emerge.log to get information about last emerge,
match emerge to logfiles in /var/log/portage (provided you enabled
logging), and display them in a readable fashion.
Maybe something similar should be added to portage?
[-- Attachment #2: portage-log-parse.py --]
[-- Type: application/x-python, Size: 2049 bytes --]
[-- Attachment #3: Type: text/plain, Size: 45 bytes --]
--
gentoo-portage-dev@gentoo.org mailing list
reply other threads:[~2004-10-16 23:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=921ad39e041016164269135cfa@mail.gmail.com \
--to=hackeron@gmail.com \
--cc=gentoo-portage-dev@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