On Thu, 6 Dec 2012 12:28:37 -0500
Mike Gilbert <floppym@gentoo.org> wrote:

> On Thu, Dec 6, 2012 at 5:54 AM, Michał Górny <mgorny@gentoo.org> wrote:
> >
> > 2) create split logs for each implementation
> >
> > Aside to the usual soup on stdout, the eclass writes separate build logs
> > for each implementation to ${T}/build-${EPYTHON}.log.
> >
> > TODO: replace tee with an awesome use of multitail to display logs
> > of currently running builds on split-screen.
> >
> 
> The split logs could be handy for developers.
> 
> I had not considered the ugly bug reports that the multi-job build
> will generate. If that becomes a major problem, we might need to
> change the default to single-job, or produce some output to point
> users to the split logs.

It would be great if we had a more general solution here. I will ask
Zac if portage could point users to all *.log files in ${T}.

On the other hand, telling user to attach up to 8 logs feels a bit bad.
But I guess they'll just put them in a tarball.

-- 
Best regards,
Michał Górny