macports error reporting, stack traces

[Bryan Blackburn]

On Mon, Nov 09, 2009 at 11:21:45PM -0800, Jordan K. Hubbard said:
> 
> On Nov 9, 2009, at 4:03 AM, Joshua Root wrote:
> 
> > On 2009-11-9 14:13, Jordan K. Hubbard wrote:
> >> On Nov 8, 2009, at 10:03 AM, Jeremy Lavergne wrote:
> >> 
> >>> Should we add the typical steps for producing debug error logs to the output of the standard trace during a failure?
> >> 
> >> That certainly sounds like something that should be documented, though one would almost wish to then render that documentation obsolete by dumping debug output on error.  In other words, ui_debug would always generate debug information, the Debug flag merely indicating what the output fd was.  If not set, it's set to some temporary file which has already been unlinked (the open, unlink truck) but has a fd that can be rewound and copied to stderr on error, and if it's set then the fd points directly to stderr.  Whatever routine catches errors for a port build would be responsible for dumping the error log.  Sounds like an excellent Tcl / MacPorts base beginner's project. :)
> > 
> > That is exactly what the gsoc09-logging branch does.
> 
> Even more awesome!   When's that scheduled for completion and merge with trunk? :-)

In r60372, now that I figured out the oddity from svn merge with a few files
with their own svn:mergeinfo properties...

'port help log' is a good place for people to start with it.

Bryan


> 
> - Jordan