NAME
pakfire - The package management system for IPFire
SYNOPSIS
pakfire check pakfire clean pakfire execute [--bind PATH] [--non-interactive] COMMAND pakfire info [--long] PACKAGE [PACKAGE ...] pakfire install [--without-recommended] [--allow-uninstall] [--allow-downgrade] [--replace-files] PACKAGE [PACKAGE ...] pakfire key TODO pakfire provides [FEATURE] pakfire requires [FEATURE] pakfire remove [--keep-dependencies] PACKAGE [PACKAGE ...] pakfire repo add [--yes] ~USER/REPO | ~USER/DISTRO/REPO pakfire repo remove ~USER/REPO | ~USER/DISTRO/REPO pakfire repolist pakfire search PATTERN pakfire sync [--keep-orphaned] [--without-recommended] pakfire update [--exclude PATTERN|-x PATTERN] [--without-recommended] [--allow-uninstall] [--allow-downgrade] [--replace-files] [PACKAGE ...]
DESCRIPTION
pakfire is the command that controls the IPFire Package Management system.
OPTIONS
- --version
-
Prints the software version and exits.
- --config FILE
- -c FILE
-
Load a custom configuration file. See pakfire-conf(5) for more details.
- --enable-repo REPO
- --disable-repo REPO
-
Enables/disables a repository that is disabled/enabled in the configuration.
- --offline
-
Enable offline mode. Pakfire will not try to refresh any repository information or perform any file downloads.
- --debug-solver DIR
-
Writes a testcase of every run of the solver into a new directory below DIR. It can be replayed with testsolv(1) from libsolv to reproduce what the solver has decided, for example to report a problem.
- --arch ARCH
-
Run Pakfire for a different architecture. This might run emulation which has degraded performance.
- --root PATH
-
Run Pakfire in a different path. This is useful when you want to setup, debug, or fix a different system. Can be used in combination with --arch.
COMMANDS
- check
-
This command checks the integrity of the installation. If any errors are returned they can be fixed with the sync command.
- clean
-
Cleans all temporary and downloaded files.
- execute [--bind PATH] [--non-interactive] COMMAND
-
Executes a command inside a Pakfire environment (useful in combination with --root= and --arch=).
--non-interactive makes the shell non-interactive and using --bind parts of the local file system can be made available inside the environment. - info [--long] PACKAGE [PACKAGE …]
-
Shows information about the given package. --long will show additional information.
- install [--without-recommended] [--allow-uninstall] [--allow-downgrade] [--replace-files] PACKAGE [PACKAGE …]
-
Installs one or more packages.
By default, Pakfire installs packages that are recommended for use with the installed set of packages. A recommended package that has been removed is not being installed again when what recommends it is being updated. Packages that the hardware needs (e.g. the microcode for the processor) are being installed even if they have been removed before. All of this can be disabled with --without-recommended.
If the package cannot be installed due to dependency problems, the solver can be allowed to allow uninstalling other packages (--allow-uninstall) or to downgrade already installed packages (--allow-downgrade).
Packages are not being installed if they have a file that another package has with different content. With --replace-files, this is only being reported and the file of the package that is installed last replaces the other one. - key
-
TODO
- provides [FEATURE]
-
Shows a list of packages that provide a certain feature.
- requires [FEATURE]
-
This shows a list of all packages that require a certain feature. The operating is basically the opposite of provides.
- remove [--keep-dependencies] PACKAGE [PACKAGE …]
-
Uninstalls the given package and all dependencies that are no longer needed. Those can be kept using the --keep-dependencies switch.
- repo add [--yes] ~USER/REPO | ~USER/DISTRO/REPO
-
Adds a repository of a user of the build service, which is called what the build service calls it: ~ms/test is the repository test of the user ms in the distribution of this system, and ~ms/ipfire-3/test says which distribution that is.
The configuration is fetched from the build service and stored with the other repositories (/etc/pakfire/repos/ms-test.repo), where ms-test is the name that it is called by in the configuration, which does not clash with the repositories of others.
This is a repository of somebody else, from which packages are going to be installed. That is why it is shown whose repository it is and with which key its packages are signed (the fingerprint), and you are asked if you trust it. --yes (also as the global option) adds it without asking. Without a terminal, nothing is added unless --yes is given.
Adding a repository again updates its configuration. - repo remove ~USER/REPO | ~USER/DISTRO/REPO
-
Removes a repository that has been added with repo add (the name in the configuration, like ms-test, works, too).
- repolist
-
Shows information about all available repositories and their configuration.
- search PATTERN
-
Searches for packages that match PATTERN. Globbing can be used.
- sync [--keep-orphaned] [--without-recommended]
-
Synchronises the local system with the upstream repositories. All packages will be updated to their latest version and orphaned packages will be uninstalled. --keep-orphaned disables this behaviour.
See install on --without-recommended. - update [--exclude PATTERN|-x PATTERN] [--without-recommended] [--allow-uninstall] [--allow-downgrade] [--replace-files] [PACKAGE …]
-
Updates all installed packages to their latest versions. If packages are passed, only those and their dependencies will be updated.
Using --exclude or -x allows excluding one or more packages that won’t be updated.
See install on --without-recommended, --allow-uninstall, --allow-downgrade and --replace-files.
BUG REPORTS
Please report all bugs to the bugtracker at https://bugzilla.ipfire.org/; refer to https://wiki.ipfire.org/devel/bugzilla for details.
AUTHORS
Michael Tremer