Free BSD’s response has always been, (not actual quote), “We have the ports collection, which is cooler and more flexible than just having some easy to use package manager.
You can always do it yourself by writing scripts around the pkg_* tools or using portmaster’s –packages-only option”.
OPTIONS The following options are supported by pkg add: ENVIRONMENT The following environment variables affect the execution of pkg add. ASSUME_ALWAYS_YES HANDLE_RC_SCRIPTS PKG_DBDIR FILES See pkg.conf(5). SEE ALSO pkg(8), pkg-audit(8), pkg-autoremove(8), pkg-backup(8), pkg-check(8), pkg-clean(8), pkg-create(8), pkg-delete(8), pkg-fetch(8), pkg-info(8), pkg-install(8), pkg-query(8), pkg-register(8), pkg-repo(8), pkg-rquery(8), pkg-search(8), pkg-set(8), pkg-shell(8), pkg-shlib(8), pkg-stats(8), pkg-update(8), pkg-updating(8), pkg-upgrade(8), pkg-version(8), pkg-which(8), pkg.conf(5) Free BSD 10.0 June 12, 2012 Free BSD 10.0 The last man page listed above is for pkg.conf, this is the system-wide confutation file for pkgng’s pkg tools. For more information on the syntax of YAML, please visit the official YAML website –
Bsd pkgupdating date
Free BSD has been long due a better package management system, pkg_add, pkg_info, etc just doesn’t cut it any more.
For a long time GNU/linux users have always used this as a reason not to use Free BSD and instead favour some GNU/linux combination with an all encompassing easy to use package manager, such as Debian’s apt-get.
To get pkgng working you must first configure a PACKAGESITE in /usr/local/etc/pkg.conf, or you will get an error like this: In the near future this value will be set automatically.
If you want to test upgrading packages you might want to start with PACKAGESITE defined to and then change it to the above when you want to test upgrades.
You can now update pkgng from the remote repository database. done ************************************************************************ Remember to run mysql_upgrade (with the optional --datadir= Note: pkg install runs pkg update before attempting to install anything.
# pkg search mysql-server mysql-server-5.1.65 Multithreaded SQL database (server) mysql-server-5.0.95 Multithreaded SQL database (server) mysql-server-4.1.25 Multithreaded SQL database (server) mysql-server-5.5.27 Multithreaded SQL database (server) # pkg install mysql-server-5.5.15 Updating repository catalogue Repository catalogue is up-to-date, no need to fetch fresh copy The following packages will be installed: Installing mysql-client: 5.5.27 Installing mysql-server: 5.5.27 The installation will require 116 MB more space 10 MB to be downloaded Proceed with installing packages [y/N]: mysql-client-5.5.27100% 1493KB 1.5MB/s 1.5MB/s mysql-server-5.5.27100% 8691KB 8.5MB/s 6.5MB/s Checking integrity... done Installing mysql-server-5.5.27...=== Creating users and/or groups. As you can see pkgng will find any dependencies it needs and install them.
Before it actually does anything it will show you what it is going to do as well as how much disk space will be used and how much data will be downloaded. The pkg add command is a little bit like pkg install but don’t get them confused, they are quite different.
pkg add requires a full path to the package file to install whether that is local or remote.
Here’s an exmaple of the help command and the available man pages.
DESCRIPTION pkg add installs a package from either a local source or a remote one.
Pkgng has it’s own way of keeping track of installed packages.