Updating the pkgdb

6854933580_2c8b688306_z

If the database is outdated but you do not have permission to update it, it delegates tasks to pkg_info(1).

Actually, pkgdb and pkg_which are the same command, and are equivalent.

It maintains a hash that maps an installed file to a package name, a hash that maps a package to an origin, and a list of installed packages.

pkg_which looks in the package database to tell which package each speci- fied file came from.

Repositories are the heart of the xbps package system.

Repositories can be locally or remotely available: $ xbps-query -Rs void-repo [*] void-repo-debug-5_1 Void Linux drop-in file for the debug repository [*] void-repo-multilib-5_1 Void Linux drop-in file for the multilib repository [*] void-repo-multilib-nonfree-5_1 Void Linux drop-in file for the multilib/nonfree repository [*] void-repo-nonfree-5_1 Void Linux drop-in file for the nonfree repository This will update all currently installed packages to the latest version found in the registered repositories, performing a global system update.

Some highlights: The Rosetta stone table may help you find the right commands quickly, if you know your way around in other main distro families.

You should run this command periodically so portupgrade(1) and other pkg_* tools can work effectively and reliably.

OPTIONS The following command line arguments are supported: file Inquire which package file came from.

Beware that this may reduce significantly the response time, it is advise to use it in combinaition with a specifir branch.

Defaults to False.a boolean to specify whether to include results for EOL collections or not. If True, it will return results for all collections (including EOL).

a boolean to specify whether to include results for EOL collections or not. If True, it will return results for all collections (including EOL).

You must have an account to comment. Please register or login here!