Hitchhiker's Guide to Openbsd

15.3.7 - Uninstalling a port's package
It is very easy to uninstall a port: 
$ make uninstall
===> Deinstalling for rsnapshot-1.2.9
rsnapshot-1.2.9: complete
Clean shared items: complete
This will call pkg_delete(1) to have the corresponding package removed from your system. If desired, 
you can also uninstall and re-install a port's package by using 
$ make reinstall
===> Cleaning for rsnapshot-1.2.9
/usr/sbin/pkg_delete rsnapshot-1.2.9
rsnapshot-1.2.9: complete
Clean shared items: complete
===> Installing rsnapshot-1.2.9 from /usr/ports/packages/
i386/all/rsnapshot-1.2.9.tgz
http://www.openbsd.org/faq/faq15.html (18 of 27)9/4/2011 10:02:29 AM

---

15 - The OpenBSD packages and ports system
rsnapshot-1.2.9: complete
If you would like to get rid of the packages you just built, you can do so as follows: 
$ make clean=packages
===> Cleaning for rsnapshot-1.2.9
rm -f /usr/ports/packages/i386/all/rsnapshot-1.2.9.tgz
15.3.8 - Using flavors and subpackages
Please do read the 
ports(7)
 manual page, which gives a good overview of this topic. There are two 
mechanisms to control the packaging of software according to different needs. 
The first mechanism is called flavors. A flavor usually indicates a certain set of compilation options. For 
instance, some applications have a "no_x11" flavor which can be used on systems without X. Some 
shells have a "static" flavor, which will build a statically linked version. There are ports which have 
different flavors for building them with different graphical toolkits. Other examples include: support for 
different database formats, different networking options (SSL, IPv6, ...), different paper sizes, etc. 
Summary: Most likely you will use flavors when a package has not been made available for the flavor 
you are looking for. In this case you will specify the desired flavor and build the port yourself. 
Most port flavors have their own working directory during building and every flavor will be packaged 
into a correspondingly named package to avoid any confusion. To see the different flavors of a certain 
port, you would change to its subdirectory and issue 
$ make show=FLAVORS
You should also look at the port's DESCR files, as they're supposed to explain the available flavors. 
The second mechanism is called subpackages. A porter may decide to create subpackages for different 
pieces of the same application, if they can be logically separated. You will often see subpackages for the 
client part and the server part of a program. Sometimes extensive documentation is bundled in a separate 
subpackage because it takes up quite some disk space. Extra functionality that pulls in heavy 
dependencies will often be packaged separately. The porter will also decide which subpackage is the 
main subpackage, to be installed as a default. Other examples are: extensive test suites which come with 
the software, separate modules with support for different things, etc.