Bug 394939

Summary:	emerge.log shows emerge leaked arguments (--quiet-build=? --package-moves=?)
Product:	Portage Development	Reporter:	Jeroen Roovers (RETIRED) <jer>
Component:	Core	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	trivial
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Jeroen Roovers (RETIRED) gentoo-dev

2011-12-16 14:12:10 UTC

Example

1324044580: Started emerge on: Dec 16, 2011 15:09:40
1324044580:  *** emerge --package-moves=n --ask --quiet-build=n --nodeps --verbose app-misc/mc

I've been seeing this for a long time and thought I might ask for a bit of polishing up of what gets into emerge.log. Note that in this case --quiet-build=n is part of EMERGE_DEFAULT_OPTS, while --package-moves=n was set as a command line argument. I guess neither should show up in emerge.log.

Comment 1 Zac Medico gentoo-dev

2011-12-16 17:36:54 UTC

I think the point of showing the options in the log is to show the "effective" options, not just the ones that happen to be given on the command line. If we omit options from EMERGE_DEFAULT_OPTS, then should probably omit all options.