When comparing pkgsrc vs CodeKit, the Slant community recommends CodeKit for most people. In the question“What are the best power user tools for macOS?” CodeKit is ranked 21st while pkgsrc is ranked 52nd. The most important reason people chose CodeKit is:
Everything you need to get a project started is included with CodeKit. Thanks to the professional support, different components of the workflow pipeline are guaranteed to play nicely with each other without you needing to do the research on how to configure them. More advanced features that may require extra configuration to set up with other workflow wrappers are set up out of the box in CodeKit, like automatic browser updating, linting, and source maps.
Ranked in these QuestionsQuestion Ranking
Pro pkgin is an apt-like tools for installing binaries from pkgsrc
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.
Pro Offering tooling for backporting fixes
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.
Pro Both binary packages and source build possible
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.
Pro Adapted for use on over a dozen different operating systems
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.
Pro Does not need Xcode command line tools or Xcode.
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.
Pro Easy installation if you use 3rd party scripts
I used this one and it worked brilliantly. https://github.com/cmacrae/savemacos
Pro Works easily with Ansible
Can be used from within Ansible to install packages on macOS.
Pro Installs and works in the same way as MacPorts
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.
Pro Everything is set up for you
Everything you need to get a project started is included with CodeKit. Thanks to the professional support, different components of the workflow pipeline are guaranteed to play nicely with each other without you needing to do the research on how to configure them.
More advanced features that may require extra configuration to set up with other workflow wrappers are set up out of the box in CodeKit, like automatic browser updating, linting, and source maps.
Pro Provides a clean and modern GUI
CodeKit has a clean and intuitive graphical user interface out of the box. Most other tools in this category run as command line utilities or require unsupported third-party plugins to run with a GUI.
The CodeKit GUI makes it easier to navigate and manage the various components of your project with helpful UIs like dropdowns, and views that provide extra details without having to run a separate command.
Pro Live browser updating built in
CodeKit has live updating built in and will update monitored files across multiple browsers and devices, and refresh CSS without a new page load. Other workflow wrappers have live updating, but they require extra configuration. With CodeKit, everything is set up for you so you can get it up and running in no time at all.
Pro Interactively define how files compile with a GUI
You can navigate your project directory, and use a menu form to set up how it gets compiled without needing to read configuration documentation, or deal with configuration errors. On top of that, file watching and recompilation is built in with no extra configuration needed.
Pro Great value for money
At a one time cost of $29, it's a great deal considering how powerful and easy to use it is.
Pro Visual package management with Bower
CodeKit provides a clean GUI for Bower that makes it easier to navigate and get information about modules without having to deal with a command line interface.
Pro Connects with MAMP
You can use it to, for example, live-update server-side PHP by establishing a connection with your local MAMP server.
Pro Don't have to worry about vendor prefixes due to Autoprefixer support
Autoprefixer automagically adds vendor prefixes based on latest information.
Pro Reduces size of compressed images
CodeKit provides a powerful tool to automatically reduce the size of compressed images and production web code.
Pro Live pre-processor and script compilation
Pro Has over 6k componenets
Install 6,000+ Bower components with a single click: Bootstrap, jQuery, Modernizr, Zurb Foundation, even WordPress.
Con Not so broadly used on MacOS as compared with MacPorts
You do not hear about Pkgsrc as openly as you hear the words "HomeBrew" or "MacPorts"
Con Can't install some packages
Even building well known packages (except MacPorts) from source using the ports can fail.
Con Relatively complicated setup and installation
Installing and setting pkgsrc up is a bit more complicated than in other package managers where it often consists in running a single script.
Con Mac only
This is a major problem for larger teams that have varied development environments.
You get only the tools that are provided by the application.