Difference between revisions of "Pkg"

From GhostBSD Wiki
Jump to: navigation, search
(Introduction)
(Introduction)
Line 17: Line 17:
 
* Packages do not require any understanding of the process involved in compiling software on FreeBSD.
 
* Packages do not require any understanding of the process involved in compiling software on FreeBSD.
  
Sorce: [[File:Icon FreeBSD.png|50px|link=https://www.freebsd.org/doc/handbook/ports-overview.html]]'''4.2. Overview of Software Installation'''
+
Sorce: [[File:Icon FreeBSD.png|50px|link=https://www.freebsd.org/doc/handbook/ports-overview.html]]'''Handbook: 4.2. Overview of Software Installation'''
  
 
== Function and Examples ==
 
== Function and Examples ==

Revision as of 05:57, 29 December 2019

Application Management
pkg Software Station Update Station Ports Applications
Back to the Icon Disti GhostBSD.pngWiki


Introduction

pkg is the next generation replacement for the traditional FreeBSD package management tools, offering many features that make dealing with binary packages faster and easier. Icon FreeBSD.png

The package manager pkg is a powerful tool to manipulate pre-compiled copies of all the commands for an application, as well as any configuration files and documentation.

While the two technologies ports and packages are similar, each have their own strengths. Select the technology that meets your requirements for installing a particular application. Package Benefits

  • A compressed package tarball is typically smaller than the compressed tarball containing the source code for the application.
  • Packages do not require compilation time. For large applications, such as Mozilla, KDE, or GNOME, this can be important on a slow system.
  • Packages do not require any understanding of the process involved in compiling software on FreeBSD.

Sorce: Icon FreeBSD.pngHandbook: 4.2. Overview of Software Installation

Function and Examples

A package can be manipulated with the pkg(8) commands, such as pkg install.

pkg only works with binary packages. By default, pkg uses the binary packages from the GhostBSD/TrueOS package mirrors. "GhostBSD now use TrueOS packages base from ports" [1].

Each pkg command argument is documented in a command-specific manual page. To read the manual page for pkg install, for example, run either of these commands:

# pkg help install

or

# man pkg-install

Installing Packages

To install a binary package use the following command, where packagename is the name of the package to install:

# pkg install packagename

This command uses repository data to determine which version of the software to install and if it has any uninstalled dependencies.

Removing Packages

Packages that are no longer needed can be removed with pkg delete. For example:


# pkg delete packagename

Upgrading Installed Packages

Installed packages can be upgraded to their latest versions by running:

# pkg upgrade

This command will compare the installed versions with those available in the repository catalogue and upgrade them from the repository.

Auditing Installed Packages

Software vulnerabilities are regularly discovered in third-party applications. To address this, pkg includes a built-in auditing mechanism. To determine if there are any known vulnerabilities for the software installed on the system, run:

# pkg audit -F

Automatically Removing Unused Packages

Removing a package may leave behind dependencies which are no longer required. Unneeded packages that were installed as dependencies (leaf packages) can be automatically detected and removed using:

# pkg autoremove

For more Information

Source: *FreeBSD Handbook/chapter 4.4. Using pkg for Binary Package Management