On Oct 16, 2009, at 13:09, Scott Haneda wrote:
This is how problems go...
1) port install foo
2) error
3) email mailing list, get advice
4) port -d install foo
5) email -d log to mailing list
6) profit
Why can't macports always run a debug log, not to stdout, but to an
install.log, that was perhaps rotated, or kept the last install at
least.
That would be what the GSoC '09 logging project was all about.
http://trac.macports.org/wiki/SummerOfCode#logging
Did that ever get done?
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users