On Nov 16, 2015, at 14:01, Clemens Lang wrote: > On 16 Nov, 2015, at 20:52, Ryan Schmidt wrote: > >> Enabling trace mode by default would solve a lot of problems. Where are we >> with >> that? What outstanding issues remain? Is there a (hidden?) macports.conf >> option >> I can use to always enable trace mode or do I have to remember to use the >> "-t" >> flag with every port command? > > The overhead of trace mode is currently somewhere around 75% (although a > couple > measurements would be nice).
75% sounds like a lot. 75% of what? Are we saying that port builds take 75% longer? > IMO trace mode should get faster using client-side > caching mechanisms, possibly shared between different processes, before we > enable > it by default. What kind of caching? _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
