For those that prefer not to leave a mess on their file system, nor have default permissions changed and security degraded, nor have Google Analytics snooping on them, would prefer access to upwards of six times as many packages, would prefer an easy choice between binary install and full source build including dependencies built from source, and would prefer a more recent version (1.6 < 1.6.1), and/or are a recovering alcoholic, innoextract has been available on MacPorts[1] since January 2019.
> For those that prefer not to leave a mess on their file system ... innoextract has been available on MacPorts[1] since January 2019.
Speaking of making a mess, instead of somewhat vague sniping, you could have made it clear that your beef is with Homebrew, rather than risking the impression that it's with this neat Quake 1 port. Because at the moment you have the top rated comment and it looks like you're slagging off this project rather than making a potentially valid argument for Macports over Homebrew.
The project author probably chose Homebrew because they already knew how to use it, it works, and they were more interested in making their Quake port than with evaluating different package managers. People make these kinds of choices all the time, particularly with side projects where they only have limited time to work on them.
> it looks like you're slagging off this project rather than making a potentially valid argument for Macports over Homebrew.
It looks like you're personally attacking me rather than speaking to any argument I may have made.
> The project author probably chose Homebrew because they already knew how to use it, it works, and they were more interested in making their Quake port than with evaluating different package managers. People make these kinds of choices all the time, particularly with side projects where they only have limited time to work on them.
As I made no mention of the author nor the project, and no one but the author knows the reasons for their choices, this is a mind-reading fallacy wrapped in a straw man.
And in general it does everything as user not su for a few years now. (Actually a good idea if using it before M1 to brew dump, remove installs and brew, then reinstall from the dumped brew file.)
The issue is that by default on install Homebrew uses Google Analytics.
> And in general it does everything as user not su for a few years now.
Homebrew always did everything as the admin user and not as root, and that was always the problem. It mungs permissions of /usr/local; all files, not just directories. And it's not so much of a package manager as it is a needless frontend for git. MacPorts, alternatively, respects default file system ownership, is a full-featured package management system, and like pkgsrc, is based on the FreeBSD ports system.
And when uninstalled, MacPorts doesn't leave a mess. With these 3 commands, it leaves no trace (with the exception of the /opt directory in the event it is used for something else):
sudo port -vfp uninstall --follow-dependencies installed
sudo port -vfp uninstall all
sudo rm -rf /opt/local /Library/Tcl/macports*
If the day ever comes, good luck uninstalling Homebrew.[1][2]
[1] https://www.macports.org/install.php