Bug 124165 – sys-apps/portage-2.1_pre5 and PORTAGE_ELOG_SYSTEM="save"

• Status: RESOLVED FIXED
• Product: Portage Development

[Description jieryn 2006-02-26 06:15:52 UTC]

the PORTAGE_ELOG_SYSTEM="save" option should use PORT_LOGDIR, if enabled, as the destination of logfiles instead of PORTAGE_TMPDIR. i think this is a great feature, but we could be a little bit smarter.. :-)

[Comment 1 Bjarke Istrup Pedersen (RETIRED) 2006-02-26 13:22:08 UTC]

I vote for that too :-)

[Comment 2 Marius Mauch (RETIRED) 2006-02-26 15:39:48 UTC]

Actually I didn't use PORT_LOGDIR on purpose to keep the different kinds of portage logs separate, though that code isn't set in stone yet, using $PORT_LOGDIR/elog would probably satisfy both goals.

[Comment 3 jieryn 2006-02-26 15:45:57 UTC]

perhaps this is rapdily spinning beyond your original vision but...  if the 'mail' option splits all the status messages per build, why not be consistent with the other logging functionality.. that is, one for each of the last builds? :-)

[Comment 4 Marius Mauch (RETIRED) 2006-02-26 15:48:27 UTC]

(In reply to comment #3)
> perhaps this is rapdily spinning beyond your original vision but...  if the
> 'mail' option splits all the status messages per build, why not be consistent
> with the other logging functionality.. that is, one for each of the last
> builds? :-)

Sorry, can't follow you there. How does 'mail' split things differently to 'save'?

[Comment 5 jieryn 2006-02-26 15:54:08 UTC]

i've errored, sorry!

[Comment 6 Sam 2007-08-12 18:27:24 UTC]

At the moment elog uses PORT_LOGDIR/elog, fixing this bug. I assume it can be closed?

[Comment 7 Zac Medico 2007-08-12 19:22:21 UTC]

Thanks, apparently this has been fixed.