LinuxCommandLibrary

gdebi

Install local .deb packages with dependency resolution

TLDR

Install local .deb packages resolving and installing its dependencies

$ gdebi [path/to/package.deb]
copy

Do not show progress information
$ gdebi [path/to/package.deb] [[-q|--quiet]]
copy

Set an APT configuration option
$ gdebi [path/to/package.deb] [[-o|--option]] [APT_OPTS]
copy

Use alternative root dir
$ gdebi [path/to/package.deb] --root [path/to/root_dir]
copy

Display version
$ gdebi --version
copy

SYNOPSIS

gdebi [OPTION...] PACKAGE.DEB...

PARAMETERS

-n, --no-install
    Do not actually install the package; only resolve dependencies.

-q, --quiet
    Suppress progress indicators and most output during operation.

--apt-line
    Simulate the installation and output a line suitable for apt-get to install the package and its dependencies.

--non-interactive
    Do not ask questions during installation; useful for scripting and automated environments.

--help
    Display a brief help message and exit.

--version
    Display the version information for gdebi and exit.

DESCRIPTION

The gdebi command is a lightweight tool designed to install local Debian (.deb) package files. Its primary advantage over dpkg is its ability to automatically resolve and install package dependencies from configured APT repositories. While dpkg can install .deb files, it will fail if dependencies are not met, leaving the user to manually find and install them. gdebi bridges this gap by performing a dependency check and then using APT's mechanisms to fetch and install any required packages, much like apt install would for repository packages. It provides a more user-friendly and complete experience for installing downloaded .deb files.

CAVEATS

gdebi relies on your system's configured APT repositories to find and install dependencies. If a dependency is not available in these repositories (e.g., a custom library), gdebi will not be able to resolve it. It is primarily designed for installing single local .deb files, not for managing large sets of packages or complex repository interactions.

GUI FRONT-END

gdebi also has a graphical user interface (GUI) counterpart, typically named gdebi-gtk or simply 'GDebi Package Installer'. This GUI application provides a visual way to inspect a .deb package, view its dependencies, and then proceed with installation, offering an even more user-friendly experience for desktop users.

TYPICAL USAGE

The most common use case for gdebi is when you download a .deb package directly from a software vendor's website (e.g., Google Chrome, VS Code). Instead of manually checking and installing dependencies, you can simply run gdebi on the downloaded file, and it will handle the rest, ensuring all necessary components are present before the main package is installed.

HISTORY

gdebi was developed to address a common pain point for Linux users: installing locally downloaded .deb packages while automatically handling their dependencies. Before its widespread use, users often had to resort to complex dpkg commands followed by apt-get -f install to fix dependency issues. gdebi streamlined this process, particularly benefiting users who frequently install software not available directly in official repositories. Its development provided a simpler, more intuitive way to integrate external applications into the system, often becoming the default application for opening .deb files in desktop environments.

SEE ALSO

dpkg(1), apt(8), apt-get(8), aptitude(8)

Copied to clipboard