[gentoo-dev] logging in portage

[gentoo-dev] logging in portage

[Rufiao Valhacouto]

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?

Re: [gentoo-dev] logging in portage

[George Shapovalov]

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?

Re: [gentoo-dev] logging in portage

[Alexander Holler]

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.

Alexander

Re: [gentoo-dev] logging in portage

[Rufiao Valhacouto]

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.  

Re: [gentoo-dev] logging in portage

[Rufiao Valhacouto]

On Mon, 2002-06-10 at 03:17, George Shapovalov wrote:
> 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...

I've written such a [sh] script, and it's not quite straightforward due
to the text manipulations it needs to do in the emerge text output
(maybe it could be better by writing it in python directly interfacing
with portage.py). Anyway, it seems for me it'd be nice to have the build
output of every single package in the system (in other words, be part of
the framework), not only for the ones processed by the logging script.

> 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'll post it to bugs.gentoo.org. Please contact me if you think I could
help providing code for this.

Re: [gentoo-dev] logging in portage

[Rufiao Valhacouto]

On Mon, 2002-06-10 at 03:17, George Shapovalov wrote:
> 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.

Added bug #3585. Please review.