List Archive: gentoo-project
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Monday 05 December 2011 17:13:26 Chí-Thanh Christopher Nguyễn wrote:
> Mike Frysinger schrieb:
> >> Not all failures are errors, only errors are shown
> > all failures as characterized by "ebuild called `die`" get shown --
> > portage dumps the entire log, thus your need to copy & paste the log
> > file to `cat` is garbage.
> > all "failures" that don't result in an aborted build (e.g. EAPI=0 dodoc
> > on missing file) will get "missed". many of those are logged as QA
> > warnings, but it seems default --quiet-build=y will not include these in
> > the log summary. this might be useful to fix -- i'll poke Zac about it
> > if he doesn't see this e- mail.
> > otherwise, your statement is really way too zen to get anything
> > meaningful out of it. post actual examples of what you're talking
> > about.
> Attached you will find a build.log of trying to build cdrtools on
> sparc-solaris prefix. Admittedly a bit exotic, but far from unique
> A moderately knowledgeable user would notice that something is wrong
> from watching the build output for a couple of seconds. Portage however
> proceeds happily because make returns exit status 0.
portage would always proceed. the only thing that would stop it is the user
hitting CTRL+C. and that requires the user actually be watching the build
output. perhaps they would be for a single package, but for general upgrades,
i doubt you can rely on that. what would be more likely is they try to run
`cdrecord`, find it missing, find the build failed, and then file a bug. that
workflow really isn't affected by the defaults here.
signature.asc (This is a digitally signed message part.)