Hey, does anybody know what the current state of trace mode in MacPorts is?
The code seems old, but contrary to my expectations the bit rod doesn't seem to have broken it completely (e.g., segfaulting or similar). >From my tests, it seems most things work, but checks against dependencies fail, because the registry might not be open. Is anybody still using trace mode? Does anybody remember what performance impact trace mode had? Is having a working trace mode a good idea? Should we try to get it back working and optimize it to a point where it can be turned on globally? (I'm thinking about avoiding conflicts with /usr/local, especially brew here.) Maybe it could also be used as replacement for "How to test" in http://trac.macports.org/wiki/UsingTheRightCompiler? -- Clemens Lang _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
