Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: virt_always_ex…
Fetching contributors…

Cannot retrieve contributors at this time

187 lines (134 sloc) 6.221 kb
Generated from $Fink: usage.xml,v 1.14 2004/03/05 15:40:26 fingolfin Exp $
Fink Usage
============
Setting The Paths
-------------------
To use the software installed in Fink's directory hierarchy, including the
fink command itself, you must set your PATH environment variable (and some
others) accordingly. Shell scripts are provided to do this for you. If you
use tcsh, add the following to your .cshrc:
source /sw/bin/init.csh
Editing .cshrc will only affect new shells (i.e. newly opened Terminal
windows), so you should also run this command in all Terminal windows that
you opened before you edited the file. You'll also need to run "rehash"
because tcsh caches the list of available commands internally.
If you use a Bourne type shell (e.g. sh, bash, zsh), use instead:
source /sw/bin/init.sh
Note that the scripts also add /usr/X11R6/bin and /usr/X11R6/man to your
path so you can use X11 when it is installed. Packages have the ability to
add settings of their own, e.g. the qt package sets the QTDIR environment
variable.
Using Fink
------------
Fink has several commands that work on packages. All of them need at least
one package name, and all can handle several package names at once. You can
specify just the package name (e.g. gimp), or a fully qualified name with a
version number (e.g. gimp-1.2.1 or gimp-1.2.1-3). Fink will automatically
choose the latest available version and revision when they are not
specified.
What follows is a list of commands that Fink understands:
install
---------
The install command is used to install packages. It downloads, configure,
builds and installs the packages you name. It will also install required
dependencies automatically, but will ask you for confirmation before it does
so. Example:
fink install nedit
Reading package info...
Information about 131 packages read.
The following additional package will be installed:
lesstif
Do you want to continue? [Y/n]
Aliases for the install command: update, enable, activate, use. (Most of
these for historic reasons.)
remove
--------
The remove command removes packages from the system by calling 'dpkg
--remove'. The current implementation has some flaws: It only works on
packages Fink knows about (i.e. where an .info file is present); and it
doesn't check dependencies itself but rather completly leaves that to the
dpkg tool (usually this poses no problem, though).
The remove command only removes the actual package files, but leaves the
.deb compressed package file intact. This means that you can re-install the
package later without going through the compile process again. If you need
the disk space, you can remove the .deb from the /sw/fink/dists tree.
Aliases: disable, deactivate, unuse, delete, purge.
update-all
------------
This command updates all installed packages to the latest version. It does
not need a package list, so you just type:
fink update-all
list
------
This command produces a list of available packages, listing installation
status, the latest version and a short description. If you call it without
parameters, it will list all available packages. You can also pass a name or
a shell pattern, and fink will list all packages that match.
The first column displays the installation state with the following
meanings:
not installed
i latest version is installed
(i) installed, but a newer version is available
Some usage examples:
fink list - list all packages
fink list bash - check if bash is available and what version
fink list "gnome*" - list all packages that start with 'gnome'
The quotes in the last example are necessary to stop the shell from
interpreting the pattern itself.
describe
----------
This command displays a description of the package you name on the command
line. Note that only a small part of the packages currently have a
description.
Aliases: desc, description, info
fetch
-------
Downloads the named packages, but does not install it. This command will
download the tarballs even if they were downloaded before.
fetch-all
-----------
Downloads _all_ package source files. Like fetch, this downloads the
tarballs even when they were downloaded before.
fetch-missing
---------------
Downloads _all_ package source files. This command will only download files
that are not present on the system.
build
-------
Builds a package, but does not install it. As usual, the source tarballs are
downloaded if they can not be found. The result of this command is an
installable .deb package file, which you can quickly install later with the
install command. This command will do nothing if the .deb already exists.
Note that dependencies are still _installed_, not just built.
rebuild
---------
Builds a package (like the build command), but ignores and overwrites the
existing .deb file. If the package is installed, the newly created .deb file
will also be installed in the system via dpkg. Very useful during package
development.
reinstall
-----------
Same as install, but will install the package via dpkg even when it is
already installed. You can use this when you accidentally deleted package
files or changed configuration files and want to get the default settings
back.
configure
-----------
Reruns the Fink configuration process. This will let you change your mirror
sites and proxy settings, among others.
selfupdate
------------
This command automates the process of upgrading to a new Fink release. It
checks the Fink website to see if a new version is available. It then
downloads the package descriptions and updates the core packages, including
fink itself. This command can only upgrade to regular releases, but you can
use it to upgrade from a CVS version to a later regular release. It will
refuse to run if you have /sw/fink set up to get package descriptions
directly from CVS.
Further Questions
-------------------
If your questions are not answered by this document, read the FAQ at the
Fink website: <http://fink.sourceforge.net/faq/>. If that still doesn't
answer your questions, subscribe to the fink-users mailing list via
<http://fink.sourceforge.net/lists/fink-users.php> and ask there.
EOF.
Jump to Line
Something went wrong with that request. Please try again.