Context Navigation

Changes between Initial Version and Version 1 of Ticket #73180, comment 46

initial	v1
2	2	> If letting MacPorts attempt to set up the Metal toolchain automatically is not considered acceptable and users (and the buildbot maintainers 😉) should always set up the Metal toolchain manually themselves, then we'd have to drop steps 3 and 4, but the actionable error message would still be an improvement over the current situation.
3	3
4		Instead of either erroring out or setting up Metal automatically MacPorts could also offer to set it up and let the user decide? If they don’t want MacPorts to do that, MacPorts could skip the port that requires it and continue with the next, instead of aborting the whole execution with an error.
	4	Instead of either erroring out or setting up Metal automatically MacPorts could also offer to set it up and let the user decide? If they don’t want MacPorts to do that, MacPorts could skip the port that requires it and continue with the next, instead of aborting the whole execution with an error. Of course, this would only be a possibility for interactive runs.