No. I'm not currently planning to add macports support. If a lot of people request it, I might consider it, but it would be a lot of work.

Tbh, I'm not sure if mixing the two in one app would make sense. Maybe a second app at one point?

I moved from macports to brew as for a long while there were no build servers for arm for macports - having to regularly build clang and gcc from source just to patch a few utilities is not much fun. But I believe that's been fixed for a while.

I honestly think brew's policy of "latest, nothing or @specialcase" isn't great for a stable work environment. But it has a lot of mind share.

In my view NixOS is too much, GNU Guix for better or worse won't support propitary toolchains like Mac, pkgsrc looks best on paper - but seems abandoned? Which leaves macports as perhaps the best option and homebrew a close second.

I find myself preferring macports for a lot of things, but homebrew has brought its own niceness to the table.

It's just a bit of a nightmare as a software author because so much rework is done to repackage your stuff in n formats: one for nix, one for guix, one for debian, one for redhat, one for homebrew, one for macports, snap, flatpak, AUR, cross-compilation for alpine, maybe add a PPA in there for the ubuntu fans...and then some of them try to wrap packages on npm, rubygems, pypi, etc.

it's all done by the community but at the same time, so many of the people you want to help with your software won't touch it if their only option is to clone the repo and compile it (which in itself is simple, if done thoughtfully)

This is one reason I like pkgsrc better on paper.

> clone the repo and compile it (which in itself is simple, if done thoughtfully)

I find rust to be fantastic in this regard. And golang is quite good as well.