Add the full build output for each package automatically to a file in the /var/db/pkg tree to allow users check what has happened in the building process. Also, add a flag to emerge/ebuild to selectively show building messages (eg. show nothing but the final result, show only errors/warnings, show everything).
Also cool would be an option to show the building output (colorized of course) in a separate xterm (when you're running under X of course), and only the general emerge output in the window you're running emerge in.
Make this proposition optional, as I just redirect the output to a log file in /tmp that gets deleted automatically after a while. I don't think it is necessary to keep al those files for a long time.
I'm actually almost done with this one. I have it as part of my threading addition to portage... I'm working on change to the spawn code so that the output is redirected to the current sys.std*'s so that I can actually log everything. It also keeps a file with status(fetching, compiling, merging) and error messages along with outputting a running activity log to the screen. output based on -vvvv and -qqqq options. (mostly relates to eprint() at the top of the emerge code) Early-ish code is http://gentoo.twobit.net/scripts/portage/ Patched against drobbin's db speedup code.
that URL is dead :/
This is actually very important.. I do emerge worlds... and there are tons of files that fly by with... Oh, you need to change the permission on this file or blah will crash .... This is rediculous... We need a curses wrapper for this, colorized, etc... with a menu/gui... keyboard or x... whatever... with split screens.. possible screens: view log file, view compiler output, status bar (oodles of possiblities here), browse the portage tree, have a shell (ala screen)... Also it could have a better etc-update editor in it...
Build log is implemented with PORT_LOGDIR, the selective output is covered by a myriad of other bugs, so I'm closing this.
it's just not resolved FIXED
