On 30 May 2017, at 17:08, Ryan Schmidt <[email protected]> wrote: > To fix this to your satisfaction, i.e. in a way that the user does not > encounter an error message that they have to fix manually, we would have to > modify every port that has such a configure script to tell it to only use the > system versions of those utilities even if the MacPorts versions are > installed. Alternately, we would have to make each of those ports declare > dependencies on each of the utilities it opportunistically uses, even if > they're not necessary. Either solution means modifying hundreds or thousands > of ports, and ensuring that newly added ports follow this strategy too. So > far, we've been unwilling to do this. > > Another solution is to use trace mode (the -t flag). Maybe one day MacPorts > can default to doing so. For now, it reduces MacPorts performance by 50% so > it's opt in rather than opt out.
When running port upgrade outdated, couldn't base just deactivate those utilities, upgrade them first and unattended rebuild broken ports/files, which is what the user eventually does manually?
