FreeBSDwiki - User contributions [en]

Portupgrade

2005-03-27T12:43:32Z

Akshat: me again.. just making commands bold

'''portupgrade and you'''

portupgrade is a small collection of tools that goes hand in hand with [[cvsup]]. Portupgrade does what it says - upgrades your ports - but it actually means your ''installed'' ports, even packages that were installed as part of the base system. Portupgrade includes two important programs - ''portupgrade'', and [[portversion]]. Between them and cvsup, you'll have the ability to keep all installed software on your system up to date, so long as it exists in the ports tree.

See also - [[cvsup]] - [[Updating the ports tree]] - [[portversion]] - [[Searching ports]]

== Installing the Portupgrade suite ==

Installation is very simple:

oyabun# '''cd /usr/ports/sysutils/portupgrade'''
oyabun# '''make install clean'''

Once it's done, you'll have to [[rehash]] or start a new session as [[root]] to use it without typing full pathnames.

== Checklist before you run portupgrade... ==

Reading /usr/ports/UPDATING first to know of important upgrades that portupgrade doesn't handle well and exactly what to do about it. A few of these fixes work much better if done _before_ you run portupgrade so it's important not to skip this step!

If you haven't done a portupgrade in a long while (i.e. a year) you're almost certain to run into situations where two or more actions have to be taken to get a port to work (doing perl5.6* -> perl5.8.1 -> 5.8.4 -> 5.8.5 being an example). You can't just assume you can do steps in any order you like; you might even have to fix some Makefiles... so read all of UPDATING before you do anything.

When done with that, you need to use [[pkgdb]] with the -F option to fix any stale dependency first.

== Using portupgrade and portversion ==

Now that that's done, you need to update your ports database.

oyabun# '''portsdb -Uu'''

This will likely take a while.

Now you can use [[portversion]] to see a list of installed programs that are out of date like so:

oyabun# '''portversion | grep \< '''
expat <
ezm3 <
fontconfig <
freetype2 <
imake <
libnet-devel <
libtool <
oyabun#

This is a possible example of the output you'd recieve from portversion. Issuing a portversion command without the ''| grep '<''' would produce a list of ALL installed packages on your machine, with '''<''' for "out of date", '''=''' for "current", and '''>''' for "newer". How can you get "newer" than what's in the ports tree? This happens if you haven't issued a '''portsdb -Uu''' command to update your ports database. The database contains entries pointing to older versions, while the ports tree itself contains newer versions, leading to situations where portversion reports ">".

Now, to upgrade one of these packages, do this:

oyabun# '''portupgrade imake'''

Portupgrade will upgrade the port with the newer version available in the ports tree, and also take care of any dependencies the new version may have - if it needed ANOTHER installed port upgraded to a newer version, for example.

That's it. You'll have to repeat these steps (portversion, then portupgrade on one of the results) a few times to complete update your software, but all in all it's fairly simple and straightforward.

Another alternative to running portupgrade manually on all of your packages would be to run the following command:
# '''portupgrade -arR'''
The -R will check the build dependencies and the -r will check the applications that depend upon the port being upgraded and the -a will upgrade all out of date ports.

Note - you may sometimes be prompted to run '''pkgdb -F''' to fix inconsistencies with listed dependencies within programs when you issue portversion commands, after upgrading ports. Just do it ('''pkgdb -F''', that is) and it will take care of the problem, allowing you to issue the portversion command.

Once done, go back to /usr/ports/UPDATING and do leftover steps to everything things to work.

== portupgrade countdown ==

On slow computers or for long-delayed updates, you might want to try '''ps | grep portupgrade''' on another screen to see how portupgrade is doing. It will get you something like this:

ruby18: portupgrade: [338/352] _name of current port_ (ruby18)

Where [338/352] means there are 352 packages being looked at and portupgrade is currently doing #338. While not every port needs an update, this command is the closest to a progress indicator you'll get for portupgrade.

The version number under _name of current port_ is the OLD version number.

== portupgrade warning ==

Interrupting portupgrade may lead to various system catastrophes such as a broken package database and inability to reach the internet to get what you need to fix it. The portupgrade command should never be interrupted. See [[Errors To Avoid]].

[[Category:System Commands]] [[Category:Ports and Packages]]

Updating the system

2005-03-09T10:07:15Z

Akshat:

'''Note''': If you only want to install security updates, it's enough to subscribe to [http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications FreeBSD security notifications] and follow the instructions in each advisory. Otherwise, read on.

In FreeBSD, the base system and ports can be updated independently if desired. Here's how to do it.

== Updating the base system ==

To upgrade to a RELEASE version of FreeBSD, you can do a binary upgrade by running '''sysinstall''' from the installation medium (e.g. CDROM). See the [http://www.freebsd.org/releases/ release notes] of the release for details.

The other option is to build from source. Note: ''This procedure is not recommended for systems in which stability is critical.'' Even if you are tracking the stable branch, occasional bugs are to be expected. For greatest stability, stick with the latest stable release version.

To update from source, first get the latest system source (/usr/src/) of the branch you're tracking (stable or current). This can be done via [[cvsup]] or [[ctm]] (see below). Then follow the steps outlined in [[upgrading the base system]].

== Updating applications ==

Many open-source apps are under active development, so this is something you'll probably want to do quite regularly to ensure that you have the latest versions of everything.

First update the ports tree (/usr/ports/). This can be done via [[cvsup]], [[ctm]] or [[portsnap]]. The ports can then be automatically updated using [[portupgrade]], which is capable of dealing with dependencies.

== How do I download updates? ==

The most common method used is [[cvsup]] (see [[updating the ports tree]]). However, you might not be able to use it if you're behind a restrictive firewall (blocking tcp port 5999) or on a weak connection. In that case you can use [[ctm]] to obtain differential updates by email or ftp.

For updating the ports tree, a third option is available. [[Portsnap]] is an automated tool which offers many advantages over both the other methods:

* secure (uses cryptographic signing)
* very efficient in terms of bandwidth consumption and server load
* uses http only
* easy to use

[[Category:Common Tasks]]

Updating the system

2005-03-06T20:19:36Z

Akshat:

'''Note''': If you only want to install security updates, it's enough to subscribe to [http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications FreeBSD security notifications] and follow the instructions in each advisory. Otherwise, read on.

In FreeBSD, the base system and ports can be updated independently if desired. Here's how to do it.

== Updating the base system ==

Note: ''This procedure is not recommended for systems in which stability is critical.'' Even if you are tracking the stable branch, occasional bugs are to be expected. For greatest stability, stick with the latest stable release version.

To update: first, get the latest system source (/usr/src/) of the branch you're tracking (stable or current). This can be done via [[cvsup]] or [[ctm]] (see below). Then follow the steps outlined in [[upgrading the base system]].

== Updating applications ==

Many open-source apps are under active development, so this is something you'll probably want to do quite regularly to ensure that you have the latest versions of everything.

First update the ports tree (/usr/ports/). This can be done via [[cvsup]], [[ctm]] or [[portsnap]]. The ports can then be automatically updated using [[portupgrade]], which is capable of dealing with dependencies.

== How do I download updates? ==

The most common method used is [[cvsup]] (see [[updating the ports tree]]). However, you might not be able to use it if you're behind a restrictive firewall (blocking tcp port 5999) or on a weak connection. In that case you can use [[ctm]] to obtain differential updates by email or ftp.

For updating the ports tree, a third option is available. [[Portsnap]] is an automated tool which offers many advantages over both the other methods:

* secure (uses cryptographic signing)
* very efficient in terms of bandwidth consumption and server load
* uses http only
* easy to use

[[Category:Common Tasks]]

Ctm

2005-03-06T19:53:26Z

Akshat:

CTM (CVS Through Mail) is a method for keeping a remote directory tree in sync with a central one. You can use it to keep both the system source and the ports tree current.

The ctm program is part of the FreeBSD base (after 2.0). To update a tree, first obtain the appropriate deltas by [ftp://ftp.freebsd.org/pub/FreeBSD/CTM/ ftp] ([http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ctm.html#MIRRORS-CTM mirrors]) or by subscribing to the right [http://lists.freebsd.org/mailman/listinfo mailing list]. The trees are:

* src-3, src-4, src-5 or src-cur for the respective stable branches or the current branch of the system base
* ports-cur for the latest port tree
* cvs-cur for the entire cvs tree

The first time you update, you will need to download the latest 'base' delta (with 'xEmpty' in its name) which can be quite large. After that you only need the small differential updates.

To update a tree (say the src-5 tree) do as root
# '''cd /usr/src'''
# '''ctm -v /path/to/downloaded/delta/src-5.xxxx.gz'''

The -v is for verbose output (see '''man ctm'''). Similarly for the ports tree you would cd to /usr/ports and run the corresponding delta through ctm.

For more options see [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ctm.html Using CTM] in the FreeBSD handbook. Also see [[updating the system]].

[[Category:System Commands]]

Portsnap

2005-03-06T19:49:01Z

Akshat:

Portsnap can be used instead of [[cvsup]] or [[ctm]] to keep the ports tree up-to-date. From the [http://www.daemonology.net/portsnap/ home page]:

----
Portsnap is a system for securely downloading and updating a compressed snapshot of the FreeBSD ports tree, and using this compressed snapshot to extract or update a (uncompressed) copy of the ports tree.

Historically, most people have used CVSup to keep their ports tree up to date, but CVSup has a number of limitations:

* CVSup is insecure. The protocol uses no encryption or signing, and any attacker who can intercept the connection can insert arbitrary data into the tree you are updating.
* CVSup isn't end-to-end. Related to the previous point, this means that anyone who can compromise a CVSup mirror can feed arbitrary data to the people who are using that mirror.
* CVSup isn't designed for frequent small updates. While CVSup is very good at distributing CVS trees, and is very efficient for updating a tree which has been significantly changed (eg, by a month or more of commits), it has transmits a list of all the files in the tree, which makes it quite inefficient if only a few files have changed.
* CVSup uses a custom protocol. This can cause problems for people behind firewalls -- outgoing connections on port 5999 need to be permitted -- and it needs a heavyweight server (cvsupd).

Portsnap avoids these problems by operating over HTTP, signing the snapshots, and using more sophisticated delta compression to distribute the snapshots.

Version 0.3.1 of portsnap is in the FreeBSD ports tree as sysutils/portsnap.
----

To install portsnap and use it for the first time:
# '''cd /usr/ports/sysutils/portsnap'''
# '''make install clean'''
# '''portsnap fetch''' (this will download a large file)
# '''portsnap extract''' (this will update the ports tree)

After that, using portsnap is easy:
# '''portsnap fetch'''
# '''portsnap update'''

See also: [[updating the system]]

[[Category:Ports and Packages]]

Ports Tree, Updating

2005-03-06T19:28:02Z

Akshat: /* It's updated. Now what? */

When updating your FreeBSD system, you'll first want to sync your sources to the live sources offered via [[cvs]]. There is a port [[cvsup]] that you can use to update your other ports and source trees if you want. If you hail from a Windows environment, you may think of keeping your sources updated as about the first half of the FreeBSD procedure which corresponds to [[Windows Update]].

== Installing cvsup ==

You'll need to have superuser access, so [[su]] to root and then go to your /usr/ports/net/ directory. There are two versions of cvsup available to you: cvsup and cvsup-without-gui (for systems that don't have or need the cvsup GUI). Pick the one that's most appropriate for you and go into that directory and "make install clean":

dave@samizdata:~% '''su -'''
Password:
samizdata# '''cd /usr/ports/net/'''
samizdata# '''ls | grep cvsup'''
cvsup
cvsup-mirror
cvsup-without-gui

so, let's say this is a headless server and I don't want X11 on it (which it is, and I don't) so:

samizdata# '''cd cvsup-without-gui/'''
samizdata# '''make install clean'''

and you'll get a ''lot'' of lines scrolling by; this is the program compiling.

== So it's installed already, how do I update the ports tree? ==

Not so fast, speed racer. First you need to configure your ''supfile''. Go to /usr/share/examples/cvsup and look through the example files. The easiest way to make a ''supfile'' for your own personal use is to copy the one that want out of the examples and edit it. So from the command line, do a
cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile
and you have just copied the ''ports-supfile'' over to the /root/ directory (root's home directory). Now you'll need to edit that file: use your favorite [[text file editor]] such as [[vi]], [[ee]] (commonly aliased under FreeBSD as "edit"), [[joe]], [[nano]], [[pico]] or [[emacs]] to edit the ''ports-supfile''.

In that file, you'll want to search for a string that says "CHANGE_THIS.freebsd.org" and change that "CHANGE_THIS" to the name of a real CVSup server. You can get a list of the servers at [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-MIRRORS the list of CVSup mirrors on freebsd.org] but they all have the general form of '''cvsup(number).(country).freebsd.org''' such as cvsup1000000.qw.freebsd.org. It will almost always make the process much faster if you choose a mirror nearest you (or the country that you're in, rather.) Save your change to the file and exit your editor. An easy way to do this is to use [[sed]]:

sed s/CHANGE_THIS.freebsd.org/cvsup#.freebsd.org/g /root/ports-supfile > /root/ports-supfile_complete

substitute a real number instead of # and ''et viola'', you've got a useful ports-supfile, named /root/ports-supfile_complete.

Once that's done, we're ready to actually update the ports. As root, issue this command:

cvsup -g -L2 /root/ports-supfile_complete

In a perfect world, that will always work. The only times when it wont are when you don't have connectivity or the server that you're cvsup-ing against is not allowing connections. Strictly speaking, the ''-g'' command isn't necessary from a command line, since I installed cvsup-without-gui and the ''-g'' switch just makes sure that the GUI stuff in the regular CVSup program doesn't run. Since it isn't installed, I could have not given the switch and the command would have run just the same. The ''-L'' switch will give you error information, as well as a sort of progress-output -- the number next to the L (2 in this case) increases or decreases the verbosity of the output (0 is totally silent and 3 will give you everything you never wanted to read and more.) The last argument of the command is the actual ports-supfile that we made.

== It's updated. Now what? ==

Well, go into /usr/ports and find stuff you want to install!

You may also want to install the very useful port management tool [[portupgrade]], which also installs a program called [[portversion]]. You can use portversion to check your existing installed programs against what is available in the ports tree, and then use [[portupgrade]] to upgrade your existing, old, installed software to the new versions found in the ports tree. Together, cvsup, portversion, and portupgrade allow you to make sure you have the latest version of ANY port in the ports tree, including packages installed with the base FreeBSD install that have been updated since your particular version was released.

See also:
* [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html The FreeBSD Handbook's section on cvsup and updating]
* [[Updating the system]]

[[Category:Common Tasks]]

Cvsup

2005-03-06T19:17:18Z

Akshat:

'''cvsup''' is the command used to synchronize the [[ports tree]] and the system [[source tree]] with the live versions at freebsd.org. '''cvsup''' stands for Concurrent Versioning System ([[cvs|CVS]]) UPdate.

Under FreeBSD, you will generally be using one of two versions of the '''cvsup''' port itself to do your synchronization; you may install /usr/ports/net/cvsup if you want to get the optional X11 GUI features, or /usr/ports/net/cvsup-without-gui if you don't plan to use X11 or otherwise don't care about the pretty windowed display (such as on a [[headless_server]]). If you choose to use the full version of cvsup, it will function precisely like the cvsup-without-gui version does if you are not running a windowing system. Please note, however, that if you don't have X installed, you do '''not''' generally want to install the full cvsup package with the gui, as it has a LOT of X-related dependencies which you utterly and completely do not need or want if you aren't running the [[X windowing system]].

For examples of the most common usages of the cvsup command, please see [[Updating the ports tree]].

[[Category : Ports and Packages]] [[Category : System Commands]]

Ctm

2005-03-06T19:13:15Z

Akshat:

Ctm

2005-03-06T19:10:53Z

Akshat:

Windows Update

2005-03-06T18:39:58Z

Akshat: removed some raw notes - the info is there in the portupgrade page

If you hail from the Windows world, one of the first questions you'll feel the need to ask about BSD is "what's the [[:Category:Windows Equivalents|equivalent]] to Windows Update?" In the FreeBSD world, the corresponding procedure is a little more complex but a LOT more powerful and comprehensive. Thanks to the ports tree, your applications as well as your base system can all be updated in the same way, and completely under your control.

The first thing you need to do is [[update the ports tree]] using [[cvsup]]. This is a CRUCIAL first step to any update process, because you want to make sure you've got the latest sources before you start compiling them to replace your existing ones!

Once you've done that, you can use the [[portupgrade]] port to first check for newer versions of installed ports and then perform the actual upgrades.

(also see [[updating the system]])

why portupgrade -a is BAD, BAD, BAD
- (why is it?)

[[Category:Windows Equivalents]]

Updating the system

2005-03-06T18:19:01Z

Akshat:

Updating the system

2005-03-06T18:17:19Z

Akshat:

Talk:Updating the system

2005-03-06T18:13:19Z

Akshat:

Hi, I'm new to FreeBSD and just joined this wiki. I thought this page was needed since I had quite a bit of trouble understanding the basic concepts of cvsup and ctm from the freebsd guide and other documentation. Please correct errors and fill in details.

-[[User:Akshat|Akshat]] 13:13, 6 Mar 2005 (EST)

Update the ports tree

2005-03-06T18:11:50Z

Akshat: Update the ports tree moved to Updating the ports tree

#REDIRECT [[Updating the ports tree]]

Talk:Update the ports tree

2005-03-06T18:11:50Z

Akshat: Talk:Update the ports tree moved to Talk:Updating the ports tree

#REDIRECT [[Talk:Updating the ports tree]]

Updating the system

2005-03-06T18:07:17Z

Akshat: see talk for comments

Note: If you only want to install security updates, it's enough to subscribe to [http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications FreeBSD security notifications] and follow the instructions in each advisory. Otherwise, read on.

In FreeBSD, the base system and ports can be updated independently if desired. Here's how to do it.

== Updating the base system ==

First, get the latest system source (/usr/src/) of the branch you're tracking (stable or current). This can be done via [[cvsup]] or [[ctm]] (see below). Then follow the steps outlined in [[upgrading the base system]].

== Updating applications ==

First update the ports tree (/usr/ports/). This can be done via [[cvsup]], [[ctm]] or [[portsnap]]. The ports can then be automatically updated using [[portupgrade]].

== Downloading methods ==

The most common method used is [[cvsup]] (see how to [[update the ports tree]]). However, you might not be able to use it if you're behind a restrictive firewall (blocking tcp port 5999) or on a weak connection. In that case you can use [[ctm]] to obtain differential updates by email or ftp.

For updating the ports tree, a third option is available. [[Portsnap]] is an automated tool which offers many advantages over both the other methods:

* secure (uses cryptographic signing)
* very efficient in terms of bandwidth consumption and server load
* uses http only
* easy to use

[[Category:Common Tasks]]

Upgrading the system

2005-03-06T16:45:10Z

Akshat:

Kernels, Custom

2005-03-06T16:11:00Z

Akshat:

==Recompiling the kernel==
The FreeBSD kernel can be recompiled in a number of simple steps. This may need to be done either while [[upgrading the base system|upgrading the system]] to a new version, to add support for various hardware not in the GENERIC kernel, or to change various kernel options. You cannot upgrade to a newer version of the kernel than the rest of the system. They must be upgraded together. This tight integration and coordination is one of the strengths of FreeBSD and contributes to its stability.

===Overview of the steps in the process===
The steps are as follows:
*Edit the kernel config file, copying it to a new name such as CUSTOM1
*Build the new kernel - make buildkernel KERNCONF=CUSTOM1
*Install the new kernel - make installkernel KERNCONF=CUSTOM1
*Reboot to test the new kernel

===More detail===
1. [[su]] to root or use [[sudo]] for every command
# su root
2. Copy the file /usr/src/sys/i386/conf/GENERIC to a new file such as /usr/src/sys/i386/conf/CUSTOM1
# cp /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/CUSTOM1
:*Edit the new file using your favorite editor such as vi, emacs, or pico. Use a # to comment out lines, but still keep the in the file for later reference. Commented out options will not be built into the kernel.
# vi /usr/src/sys/i386/conf/CUSTOM1
:*Look in the files /usr/src/sys/i386/NOTES and /usr/src/sys/??? for the various options available to add into your custom kernel file.
# more /usr/src/sys/i386/NOTES
:*Be careful which options or devices you remove from your custom config file. Don't remove any you don't understand, or at least read very carefully to learn which are needed to support others. If you remove too many and the kernel fails to build properly, assume the cause is you removed something you shouldn't have.
3. Change to the /usr/src directory to run the buildkernel command
:*You may want to use the script command to save a record of the compile in case there are any errors to report or to read and learn more about the build proces.
# cd /usr/src
# script build1
# make buildkernel KERNCONF=CUSTOM1
4. If the build process completes without errors, proceed to installing the kernel. It will automatically backup your old kernel for you. Then exit to end the scripting process, and finally reboot to test the new kernel.
# make installkernel KERNCONF=CUSTOM1
# exit
# reboot

Now you're running a new custom kernel. Try editing a new config file and remove more things or add others. Some combinations will break things, so try again. That is a great way to learn about the kernel.
[[Category:Common Tasks]]

Kernels, Custom

2005-03-06T16:10:06Z

Akshat:

==Recompiling the kernel==
The FreeBSD kernel can be recompiled in a number of simple steps. This may need to be done either while [[upgrading the system|upgrading the base system]] to a new version, to add support for various hardware not in the GENERIC kernel, or to change various kernel options. You cannot upgrade to a newer version of the kernel than the rest of the system. They must be upgraded together. This tight integration and coordination is one of the strengths of FreeBSD and contributes to its stability.

===Overview of the steps in the process===
The steps are as follows:
*Edit the kernel config file, copying it to a new name such as CUSTOM1
*Build the new kernel - make buildkernel KERNCONF=CUSTOM1
*Install the new kernel - make installkernel KERNCONF=CUSTOM1
*Reboot to test the new kernel

===More detail===
1. [[su]] to root or use [[sudo]] for every command
# su root
2. Copy the file /usr/src/sys/i386/conf/GENERIC to a new file such as /usr/src/sys/i386/conf/CUSTOM1
# cp /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/CUSTOM1
:*Edit the new file using your favorite editor such as vi, emacs, or pico. Use a # to comment out lines, but still keep the in the file for later reference. Commented out options will not be built into the kernel.
# vi /usr/src/sys/i386/conf/CUSTOM1
:*Look in the files /usr/src/sys/i386/NOTES and /usr/src/sys/??? for the various options available to add into your custom kernel file.
# more /usr/src/sys/i386/NOTES
:*Be careful which options or devices you remove from your custom config file. Don't remove any you don't understand, or at least read very carefully to learn which are needed to support others. If you remove too many and the kernel fails to build properly, assume the cause is you removed something you shouldn't have.
3. Change to the /usr/src directory to run the buildkernel command
:*You may want to use the script command to save a record of the compile in case there are any errors to report or to read and learn more about the build proces.
# cd /usr/src
# script build1
# make buildkernel KERNCONF=CUSTOM1
4. If the build process completes without errors, proceed to installing the kernel. It will automatically backup your old kernel for you. Then exit to end the scripting process, and finally reboot to test the new kernel.
# make installkernel KERNCONF=CUSTOM1
# exit
# reboot

Now you're running a new custom kernel. Try editing a new config file and remove more things or add others. Some combinations will break things, so try again. That is a great way to learn about the kernel.
[[Category:Common Tasks]]

UPDATING

2005-03-06T16:09:13Z

Akshat:

'''/usr/src/UPDATING''' is the location of the file describing all the current information needed to [[upgrading the base system|upgrade a system]] properly from source. Sometimes special procedures are needed due to recent changes in the system such as the addition of new user groups. Reading the top sections of this file is very important to successfully upgrading, and many upgrade failures are a result of users skipping this step. See also [[ /etc/make.conf]]
[[Category:Important Config Files]]

Category:Ports and Packages

2005-03-06T15:21:58Z

Akshat:

This category is intended to relate directly to binary packages and the ports tree - how to maintain and administer the package collection and ports tree themselves, which ports or packages are particularly useful, how to address problems with compiling the trickier ports or get around dependency issues with the more complex packages, et cetera.

See also: [[Installing Ports]]

note: to add an article to this category, simply append '''<nowiki>[[Category : Ports and Packages]]</nowiki>''' to the end of your article.