5.1. Using binary packages

On the cdn.NetBSD.org +

On the cdn.NetBSD.org site and mirrors, there are collections of binary packages, ready to be installed. These binary packages have been built using the default settings for the directories, that is:

@@ -1262,8 +1265,7 @@ and you can still use binary packages fr 5.1.1. Finding binary packages

To install binary packages, you first need to know from where to get them. The first place where you should look is on the main - - pkgsrc FTP server in the directory /pub/pkgsrc/packages.

This directory contains binary packages for multiple platforms. First, select your operating system. (Ignore the directories with version numbers attached to it, they just exist for @@ -1283,17 +1285,16 @@ and you can still use binary packages fr

In the directory from the last section, there is a subdirectory called All/, which contains all the binary packages that are available for the platform, excluding those - that may not be distributed via FTP or CDROM (depending on which - medium you are using).

To install packages directly from an FTP or HTTP server, run the following commands in a Bourne-compatible shell (be sure to su to root first):

-# PATH="/usr/pkg/sbin:$PATH" - -# PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages" +# PATH="/usr/pkg/sbin:/usr/pkg/bin:$PATH" +# PKG_PATH="https://cdn.NetBSD.org/pub/pkgsrc/packages" # PKG_PATH="$PKG_PATH/OPSYS/ARCH/VERSIONS/All/" # export PATH PKG_PATH +# pkg_add pkgin

Instead of URLs, you can also use local paths, for example if you are installing from a set of CDROMs, DVDs or an NFS-mounted @@ -1303,16 +1304,16 @@ and you can still use binary packages fr

Note that any prerequisite packages needed to run the +# pkgin search nginx +nginx-1.19.6 Lightweight HTTP server and mail proxy server +nginx-1.18.0nb8 Lightweight HTTP server and mail proxy server +# pkgin install zsh nginx-1.19.6 vim + +

Any prerequisite packages needed to run the package in question will be installed, too, assuming they are - present where you install from.

Adding packages might install vulnerable packages. - Thus you should run pkg_admin audit - regularly, especially after installing new packages, and verify - that the vulnerabilities are acceptable for your configuration.

After you've installed packages, be sure to have /usr/pkg/bin and /usr/pkg/sbin in your PATH so you can actually start the just @@ -1320,45 +1321,51 @@ and you can still use binary packages fr

-5.1.3. Deinstalling packages

+5.1.3. Updating packages

To update binary packages, it is recommended that you use + pkgin upgrade. This will compare the remote + package repository to your locally installed packages and safely + replace any older packages.

Note that pkgsrc is released as quarterly branches. + If you are updating to a newer quarterly branch of pkgsrc, you may + need to adjust the repository in + /usr/pkg/etc/pkgin/repositories.conf.

+5.1.4. Deinstalling packages

To deinstall a package, it does not matter whether it was - installed from source code or from a binary package. The - pkg_delete command does not know it anyway. - To delete a package, you can just run pkg_delete + installed from source code or from a binary package. Neither the + pkgin or the pkg_delete + command need to know.

+
To delete a package, you can just run pkgin remove package-name. The package - name can be given with or without version number. Wildcards can - also be used to deinstall a set of packages, for example - *emacs*. Be sure to include them in quotes, - so that the shell does not expand them before - pkg_delete sees them.
-
The -r option is very powerful: it - removes all the packages that require the package in question - and then removes the package itself. For example: - -
-
-# pkg_delete -r jpeg -
-
- - will remove jpeg and all the packages that used it; this allows - upgrading the jpeg package.
+ name can be given with or without version number.

5.1. Using binary packages

-5.1.3. Deinstalling packages

+5.1.4. Deinstalling packages

-5.1.4. Getting information about installed packages

-5.1.5. Checking for security vulnerabilities in installed packages

-5.1.6. Finding if newer versions of your installed packages are in pkgsrc

-5.1.7. Other administrative functions