From: Christian Loitsch <gentoo-dev@loitsch.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] messages at end of ebuild-scripts
Date: Tue, 12 Mar 2002 12:43:11 +0000 [thread overview]
Message-ID: <20020312124311.B27394@matrix.netsoc.tcd.ie> (raw)
I just went through my "logfiles" created with emerge xxx | tee logfile
and noticed that there are quite a few messages I just would have never
seen.
There are some ebuild-scripts which echo messages, but because emerge
just starts the next ebuild, it is nearly impossible to see them.
I think that ebuilds should never echo anything, but create info-files
(in a special directory) which I could read later on.
Another "problem" is, that, probably because my machine is only a
133MMX, emerge starts the next ebuild without flushing its output.
I always get the message "finished installing into ..."
but then it sometimes finishes the >>> output, sometimes starts the next
ebuild in the middle of a >>> line and sometimes doesn't even show one >>>
line.
christian
ps tell me if this belongs into bugzilla
reply other threads:[~2002-03-12 12:47 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=20020312124311.B27394@matrix.netsoc.tcd.ie \
--to=gentoo-dev@loitsch.org \
--cc=gentoo-dev@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