However, portsnap uses the latest/HEAD branch for the ports tree.
Since mixing quarterly packages with current ports could lead to trouble, you have to choose one of these paths: If you need the latest and greatest packages or prefer to live on the bleeding edge, option 1 is for you.
Subsequent sections of this guide will entail installing various bits of third-party software in order to augment the router's functionality.
Much of this software will be available through the Open BSD Ports Collection and package repositories.
All commands are issued as the root user or by simulating the root user by using the command Now that the Ports Collection has been updated and portmaster installed, let’s check the installed ports against the updated Ports Collection to see whether any installed ports need to be updated.
portmaster provides a way to list ports that need updating using the -L option: : Ports listed under this category have dependencies but are not depended upon by other ports.
Instead we can use CVSup protocol to quickly check out and update the entire Ports tree from any of the public Open BSD CVSup servers, which are listed here: First you'll need the # Defaults that apply to all the collections *default release=cvs *default delete use-rel-suffix *default umask=001 *default host=*default base=/usr *default prefix=/usr *default tag=OPENBSD_4_8 *default compress Open BSD-ports #Open BSD-all #Open BSD-src #Open BSD-www #Open BSD-x11 #Open BSD-xenocara This is not merely a theoretical risk.
I asked about it on the ports mailing list and got a very helpful response from Mathieu Arnold (English) that included this useful tidbit: Currently, all our tools working automatically with the quarterly branches do this before any run: latest_branch=$(svn ls https://svn.freebsd.org/ports/branches/|sed -ne '/^2.*Q./s|/$