pkgsrc vs Path Finder

pkgin aims to be a tool similar to apt/yum for managing pkgsrc binaries by relying on pkg_summary for installing, removing and upgrading packages and dependencies, using a remote repo.

Has been adopted to be used on several Unix-like operating systems and Windows. It's also the default package manager of DragonflyBSD and of the (now discounted) Bluewall Linux distro.

Installs its own dependencies which means that it is very secure. Cannot install anything unless you use the "sudo" command which is in keeping with the Unix philosophy.

Fast software installation is possible by using binary packages. It's also easy to build from source which allows for different compile-time options (like different UI backends) as well as gaining access to pre-release versions of software in certain cases.

Backporting fixes can be done by cherry-picking updates from a newer branch (pkgsrc is released every 3 months) and creating a package. Sometimes bugs need to be fixed for production and there is neither a fix in newer pkgsrc nor the softwares upstream. So pkgsrc has tools like pkgdiff, mkpatches, etc. that help with developing patches and building binary packages from that. A bit of documentation about that process can be found here.

This means that you can install it fresh on a new installation of MacOS and have all your favorite apps installed right from the start.

Can be used from within Ansible to install packages on macOS.

This one works brilliantly.

Path Finder is built around a modular interface with six customizable views. Show only the information you need, when you need it.

Path Finder can be configured to automatically open and edit word documents, text, and image files. It also has an integrated terminal, hex editor, can archive type files, and can handle file network protocols, such as ftp and afp.

Path Finder has built-in support for Git and Subversion version control systems.

A full-featured version of Path Finder can be evaluated for free for 30 days.