Package installation flowchart

Here’s an overview of what Fink needs to do in order to install a new package. A bindist (binary distribution) refers to both the .deb packages available on your local system as well as remote packages (either from Fink or from unofficial bindists).

Package installation flowchart

Package installation flowchart

As explained in a previous post, the source code is only necessary to build .deb packages, which in turn are only necessary to install files on your system. Ultimately, only the files that the package installed under /sw are needed in order to run it. However, keeping the .deb files available helps with subsequent installations and updates.

2 responses to “Package installation flowchart

  1. Alex Hansen

    The “.deb available” decision could use a bit of additional elaboration.
    fink will use a binary if a .deb is available AND if that .deb corresponds to the latest version-revision of the package. If there’s a newer (e.g. higher revision) package description, either official or through a local modification, then “fink install foo” will build foo from source.

  2. True that. Of course the same reasoning applies to source code, and if the source code corresponding to that particular version-revision of the package is available in the local system then Fink won’t fetch it.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s