Yes, I think there would be problems - people may well want to use their own compiler, especially if v9 gets released and we're still on v8.
I don't think changing the path order would be a big problem though.
Maybe a FORCE=1 option could be added, to force the compilers/etc to always be installed even if there was one already on the path?
However since this would appear to be for your tool, it might make sense to just modify your tool such that the existing gcc-arm-none-eabi was removed from your path before running provision.sh?
© Espruino, powered by microcosm.
Report a problem