How to uninstall fink

We modify Unix software so that it compiles and runs on Mac OS X "port" it and make it available for download as a coherent distribution. Fink uses Debian tools like dpkg and apt-get to provide powerful binary package management. You can choose whether you want to download precompiled binary packages or build everything from source.

Read more Support for those two releases is coming soon. The Fink Project has released fink This is a minor behavioral fix for an issue introduced in 0. This will allow installs on macOS There are no other functional changes in this release compared to fink This release provides support for all macOS releases up to and including Installing MacPorts 2. Install Xcode 2. Install MacPorts 2. Upgrade MacPorts 2. Uninstall MacPorts 2.

MacPorts and the Shell 3. Using MacPorts 3. The port Command 3. Port Variants 3. Common Tasks 3. Port Binaries 4. Portfile Development 4. Portfile Introduction 4. Creating a Portfile 4. Example Portfiles 4. Port Variants 4. Patch Files 4. Local Portfile Repositories 4. The following commands extract the archive:. That creates a directory with the same name as the archive. We'll just keep on using the placeholder fink Now, change into that directory and run the bootstrap script:. The script will run some checks on your system and use sudo to become root - that will prompt you for your password.

Then, the script will ask you for the installation path. Only that will allow you to install downloaded binary packages later on. Also, all examples use that path; be sure to substitute your actual path if you use a different one. Next up is Fink configuration. You'll be asked for things like proxy and mirror settings and whether you want verbose messages.

If you don't understand a question, just press return to accept the default choice. You can re-run this process later using the fink configure command.

When the bootstrap script has all the information it needs, it will start to download the source code for the base system and compile it. No further interaction should be necessary at this point. Don't worry if you see some packages being compiled twice. This is required because to build a binary package of the package manager, you first must have the package manager available.

In order to get a good experience and get the most out of fink you need to know a few things about Python packaging. There is now a lot of packaging infrastructure in the Python community, a lot of technology, and a lot of experience. We will try cover some basic things and give you best practice what to use for Python package management. The following diagram gives an overview on the fink packages.

Please note how we grouped the fink packages in the following categories:. At finklabs we have very few currently one fink packages we do not want to open-source. The finklabs-config-reader has very opinionated defaults on how we use fink on our AWS infrastructure that is very specific and optimized for our media usecase.

It is a very common practice not to install Python packages by hand. Instead dependencies and version are managed in a documented and repeatable way. Basically you add the names and versions of your packages to a text file. Most projects also group their dependencies into direct dependencies of the service or application and packages they need to develop, build, test and document. The grouping is not enforced by packaging but to have a std.

BTW, fink version shows you all the versions of fink and installed plugins. So you can use this to quickly check which plugins are installed.