Bsd ports updating
Fetching 90 patches.....10....20....30....40....50....60....70....80....90. This also indicates that the utility was run previously, if it was a first time run, the collection would have simply been downloaded.Since the ports are frequently updated to address security and reliability issues, you will need to periodically refresh the ports to ensure that your ports contains the latest stable set of software.The following example shows how to use the cvs utility to update the Open BSD 3.9 ports collection: $ The CVSROOT variable contains the server to connect to, the “-r” option is used to specify the Open BSD tag (each Open BSD version has a tag, and the example above contains the tag for the 3.9 release), the “-P” option causes cvs to prune empty directories, and the “ports” option indicates which repository to checkout.Once cvsup finishes grabbing the latest set of ports, the make utility can be executed to install any of the 1000s of packages under /usr/ports.
Open BSD comes with several useful software packages on teh installation media, but due to limited space the vast majority of software is provided through the Open BSD ports collection.
It does not depend upon other ports, external databases or languages, rather it’s been written in such a way as to make use of the information about a port’s dependencies, dependents, file locations and other information contained in to determine which ports to update.
The versions of software discussed in this post are as follows: Okay, let’s get started.
The ports collection includes 1000s of software packages that can be automatically downloaded, compiled, and installed.
This article will show how to configure an Open BSD system to retrieve the latest version of the ports repository, and how to build a package from the ports collection.