On Wed, Mar 4, 2015 at 6:52 AM, Chris Jones <[email protected]> wrote: > > trace mode, which blocks access to files a port should not be using (because > they have not declared a dependency) is a great tool at providing this > reproducibility. I do not see any use case for an individual port being able > to by itself opt in or out of this feature, it should be completely up to > the user running port to decide, either via a command line switch, or via > macports.conf. I would not be in favour of ports being able to forcibly opt > out, as the only reason for doing so in my opinion is because they have bugs > that should instead be fixed.
I remember discussions about enabling trace mode by default and concerns that it included a performance hit. I also seem to remember discussion about this penalty being reduced recently. Is there any reason that trace mode shouldn't be enabled by default? -- arno s hautala /-| [email protected] pgp b2c9d448 _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
