pkgsrc vs Sequel Pro
When comparing pkgsrc vs Sequel Pro, the Slant community recommends Sequel Pro for most people. In the question“What are the best power user tools for macOS?” Sequel Pro is ranked 22nd while pkgsrc is ranked 62nd. The most important reason people chose Sequel Pro is:
Clean, easy to use, highly polished interface.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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 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 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 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 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 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 Works easily with Ansible
Can be used from within Ansible to install packages on macOS.
Pro Easy installation if you use 3rd party scripts
This one works brilliantly.
Pro Great UI
Clean, easy to use, highly polished interface.
Pro Native OS X from the start
Unlike other solutions, Sequel Pro was built specifically for OS X and for MySQL from the beginning and as such the design takes better advantage of OS X features and is optimized for MySQL.
Pro Free and open source
Licensed under MIT.
Pro Multiple connection methods
Sequel Pro can choose between standard and SSH connection methods.
Pro Multiple import/export options
Sequel Pro can export to SQL, CSV and XML files and import SQL and CSV files.
Pro Command line access
Sequel Pro can also access and manage everything from the command line.
Pro Excellent user management
Has easy user privilege management.
Pro Highly flexible filters
Sequel Pro has highly flexible and customizable filters.
Cons
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 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 Outdated packages
Some packages are outdated.
Con Can't install some packages
Even building well known packages (except MacPorts) from source using the ports can fail.
Con Crashes constantly
Crashes when working with mysql 8.0.12 for macos 10.13. Unable to do anything.
Con Not maintained
The app crashes when you close a tab.
Con No MySQL 8 support
Con Not adapted for MacOS Catalina
Con No multiple query tabs
Sequel Pro does not support multiple query tabs in its editor. This is incredibly frustrating for a power user.
Con Text in the query lost on connection failure & crashes
Con OS X only, no Linux or Windows versions
Power users have to manage in many different environments. A consistent admin interface is hugely beneficial.
Con Query editing capabilities much poorer than MySql Workbench, Querious, and others
Con No visual query editor
Con Unable to import from binary SQL files
I frequently import binary multipolygon data from another source, and it won’t open.