> I personally can't use it anymore now that my MacOS version (Mojave) is not supported so everything has to build from source and Rust fails. This is pretty i

> I personally can't use it anymore now that my MacOS version (Mojave) is not supported so everything has to build from source and Rust fails. This is pretty interesting, that Homebrew abandons recent systems. I am running MacPorts on Mojave with no issues (yet). However, I am strongly considering going back to High Sierra for it's ability to build 32-bit packages, which Mojave won't do (though it will still run 32-bit applications with a warning). The only thing that keeps me from doing so immediately is that I have macOS install exhaustion. I'm a little beat up because I am doing custom macOS installs, and it takes a little effort to prevent the installer from installing all the crap I don't want. The easier way to do it is just to let it install, then remove it. I'm a little something that I prefer to go the other route, and I'm not aware of anyone else fighting the default system install to assist. I have no doubt that MacPorts runs flawlessly on High Sierra, because I have it running flawlessly on Mountain Lion, and I have a functional but frozen install of MacPorts on Snow Leopard, but I am aware there are others that have live and functional MacPorts running on Snow Leopard with a minimal amount of effort, and I'm pretty sure the same is true of Leopard, Tiger and Jaguar, though the number of users gets smaller the further back we go. It can not be overstated how awesome that is, that no system version is completely left behind. This exposes that MacPorts has some seriously resiliant development.