From: Rufiao Valhacouto <rufiao@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] logging in portage
Date: 10 Jun 2002 13:10:13 -0300 [thread overview]
Message-ID: <1023725416.6412.101.camel@tara.pvt.jagunco.net> (raw)
In-Reply-To: <177970000.1023717708@krabat.ahsoftware>
On Mon, 2002-06-10 at 11:01, Alexander Holler wrote:
> Hi,
>
> --On Sonntag, Juni 09, 2002 23:17:33 -0700 George Shapovalov
> <georges@its.caltech.edu> wrote:
>
> > It should be easy to call it inside the script you use to emerge packages
> > on this server. If you desire to make reports on a per-package basis it
> > should be easy to create the script that would run emerge --pretend
> > packagename first and then call emerge for every reported package and
> > capture reports separately...
> > WTF incorporating this into portage itself: I did not see this mentioned
> > (though there were some related things suggested). If you think this is
> > an important addition please file a feature request to bugs.gentoo.org.
>
> I would find it useful too, if warnings, comments and so on would be
> displayed and/or logged separately. Emerge could display those warnings at
> the end of the whole process (e.g. update world). So none would be getting
> lost in the mass.
The position of these warnings in the build output is sometimes
important, and it seems that splitting the build output could lose
information. A simple search in the log could point you to the warnings,
errors or anything. Anyway, it may be interesting to have an option to
show only the output warnings/errors/etc. in the interactive output.
next prev parent reply other threads:[~2002-06-10 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 0:27 [gentoo-dev] logging in portage Rufiao Valhacouto
2002-06-10 6:17 ` George Shapovalov
2002-06-10 14:01 ` Alexander Holler
2002-06-10 16:10 ` Rufiao Valhacouto [this message]
2002-06-10 16:04 ` Rufiao Valhacouto
2002-06-10 18:12 ` Rufiao Valhacouto
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=1023725416.6412.101.camel@tara.pvt.jagunco.net \
--to=rufiao@gmx.net \
--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