public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] logging in portage
  @ 2002-06-10 16:04 99%   ` Rufiao Valhacouto
  0 siblings, 0 replies; 1+ results
From: Rufiao Valhacouto @ 2002-06-10 16:04 UTC (permalink / raw
  To: gentoo-dev

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.




^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2002-06-10  0:27     [gentoo-dev] logging in portage Rufiao Valhacouto
2002-06-10  6:17     ` George Shapovalov
2002-06-10 16:04 99%   ` Rufiao Valhacouto

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox