[gentoo-user] capturing emerge output

[gentoo-user] capturing emerge output

[James]

Hello,

I have some very large emerge builds going on
with my /usr/local/portage experiments.

What would folks suggest is the best way to capture the output
from the screen into a file (fancy formating?) as well as being
able see the local builds as they scroll the build out to
the terminal (screen) window (normal emerge results viewed fromt the
terminal session ?

Is there some tools (ebuilds) for such?


Then what tools exist for parsing via a gui.

(yea I still use command line parsing visually but I figure
I ask if there are some fancy tools for an old C hack to
experiment around with......


TIA,
James

Re: [gentoo-user] capturing emerge output

[covici]

James <wireless@tampabay.rr.com> wrote:

> Hello,
> 
> I have some very large emerge builds going on
> with my /usr/local/portage experiments.
> 
> What would folks suggest is the best way to capture the output
> from the screen into a file (fancy formating?) as well as being
> able see the local builds as they scroll the build out to
> the terminal (screen) window (normal emerge results viewed fromt the
> terminal session ?
> 
> Is there some tools (ebuilds) for such?
> 
> 
> Then what tools exist for parsing via a gui.
> 
> (yea I still use command line parsing visually but I figure
> I ask if there are some fancy tools for an old C hack to
> experiment around with......
> 


I use script all the time and just  say--nocolor and --nospinner (syntax
may be off a bit) as well.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] capturing emerge output

[Douglas J Hunley]

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

On Mon, Jul 21, 2014 at 9:54 AM, James <wireless@tampabay.rr.com> wrote:

> What would folks suggest is the best way to capture the output
> from the screen into a file (fancy formating?) as well as being
> able see the local builds as they scroll the build out to
> the terminal (screen) window (normal emerge results viewed fromt the
> terminal session ?
>

sounds like a job for 'tee'


-- 
Douglas J Hunley (doug.hunley@gmail.com)
Twitter: @hunleyd                                               Web:
about.me/douglas_hunley
G+: http://google.com/+DouglasHunley

[-- Attachment #2: Type: text/html, Size: 1212 bytes --]

Re: [gentoo-user] capturing emerge output

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 573 bytes --]

On Mon, 21 Jul 2014 16:54:36 +0000 (UTC), James wrote:

> What would folks suggest is the best way to capture the output
> from the screen into a file (fancy formating?) as well as being
> able see the local builds as they scroll the build out to
> the terminal (screen) window (normal emerge results viewed fromt the
> terminal session ?

Set PORT_LOGDIR in make.conf. This is not the same as the ELOG settings,
it logs the entire output from the ebuild.


-- 
Neil Bothwick

Approx. 1 in 36000 people will break a leg within 3 weeks of reading this
post

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[gentoo-user] Re: capturing emerge output

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:


 
> > What would folks suggest is the best way to capture the output
> > from the screen into a file (fancy formating?) as well as being
> > able see the local builds as they scroll the build out to
> > the terminal (screen) window (normal emerge results viewed fromt the
> > terminal session ?
> 
> Set PORT_LOGDIR in make.conf. This is not the same as the ELOG settings,
> it logs the entire output from the ebuild.

This sound workable. If I don't want something logged, just comment 
out the PORT_LGDIR in make.conf, or is there a way on the Command line
to toggle this on and off, without manually editing the file?

I assume there is a unique log file for each separate ebuild.

Where do I read up on PORTDIR (documentation) referred to in
man make.conf ?

James

Re: [gentoo-user] Re: capturing emerge output

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

On Mon, 21 Jul 2014 23:01:44 +0000 (UTC), James wrote:

> > Set PORT_LOGDIR in make.conf. This is not the same as the ELOG
> > settings, it logs the entire output from the ebuild.  
> 
> This sound workable. If I don't want something logged, just comment 
> out the PORT_LGDIR in make.conf, or is there a way on the Command line
> to toggle this on and off, without manually editing the file?

PORT_LOGDIR="" emerge something?
 
> I assume there is a unique log file for each separate ebuild.

There is, the format is documented in man make.conf

> Where do I read up on PORTDIR (documentation) referred to in
> man make.conf ?

PORTDIR is *very* different from PORT_LOGDIR, but both are documented on
man make.conf.


-- 
Neil Bothwick

WinErr 013: Unexpected error - Huh ?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]