Re: [gentoo-dev] logging in portage

[George Shapovalov <georges@its.caltech.edu>]

Whats wrong with:
emerge pkgname &>/some/place/repfile.rep
?
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.

George


On Sunday 09 June 2002 17:27, Rufiao Valhacouto wrote:
> In the process of creating a build server (a server which is capable of
> building all the packages in the portage tree to test if a given profile
> is broken, and maybe providing binary packages for people who desire
> them) I've found it was required to have portage to be able to log the
> [per package] ebuild output into a file (more likely in the /var/db/pkg/
> tree), so that it could be analyzed later. In fact, this behavior is
> desirable generically, since it's sometimes useful to understand what
> happened in the building process of a given package. Is this
> functionality being planned for portage? Do you see any drawbacks to
> include it in the mainstream code?