On Oct 16, 2009, at 11:20 AM, Joshua Root <[email protected]> wrote:
On 2009-10-17 05: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.
If (error)
ui message: you may want to post your error log to the mailing list,
it is located at /opt/local/var/log/macports/portname-debug.log
Looking at the list archives, those 6 steps are repeated often, this
would save list admins, members, users, etc an entire set of steps,
and
get resolution of port install issues solved much faster.
<http://trac.macports.org/wiki/SummerOfCode#logging>
<http://trac.macports.org/browser/branches/gsoc09-logging>
- Josh
Very nice proposal. Glad to see it on the roadmap.
--
Scott
Iphone says hello.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
