2016-01-22 11:35:14 +00:00
2016-01-20 20:50:25 +00:00
2016-01-22 11:34:13 +00:00
2016-01-22 10:31:33 +00:00
2016-01-21 12:39:54 +00:00
2016-01-20 02:28:50 +00:00
2016-01-20 18:56:35 +00:00
2016-01-21 19:40:10 +00:00
2016-01-22 11:34:18 +00:00
2016-01-22 11:35:09 +00:00
2016-01-21 19:40:10 +00:00
2016-01-19 08:38:00 +00:00
2016-01-19 20:06:47 +00:00
2016-01-22 08:39:10 +00:00
2016-01-21 05:25:44 +00:00
2016-01-21 19:40:10 +00:00
2016-01-21 15:54:44 +00:00
2016-01-21 19:40:10 +00:00
2016-01-22 11:33:58 +00:00
2016-01-22 11:33:49 +00:00
2016-01-17 13:21:45 +00:00
2016-01-20 10:43:18 +00:00
2016-01-16 17:16:36 +00:00
2016-01-20 15:29:53 +00:00
2016-01-21 20:05:49 +00:00
2016-01-19 05:56:29 +00:00
2016-01-22 11:33:53 +00:00
2016-01-16 17:23:28 +00:00
2016-01-21 19:40:10 +00:00
2016-01-22 11:35:14 +00:00
2016-01-22 11:34:54 +00:00
2016-01-22 10:09:07 +00:00
2016-01-21 19:40:10 +00:00
2016-01-15 11:21:58 +00:00
2015-12-27 22:31:46 +00:00
2016-01-16 03:30:01 +00:00
2016-01-12 14:38:48 +00:00
2015-12-31 11:27:40 +00:00
2016-01-01 19:11:59 +00:00

This is the FreeBSD Ports Collection.  For an easy to use
WEB-based interface to it, please see:

	http://www.FreeBSD.org/ports

For general information on the Ports Collection, please see the
FreeBSD Handbook ports section which is available from:

	http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/ports.html
		for the latest official version
	or:
	The ports(7) manual page (man ports).

These will explain how to use ports and packages.

If you would like to search for a port, you can do so easily by
saying (in /usr/ports):


	make search name="<name>"
	or:
	make search key="<keyword>"

which will generate a list of all ports matching <name> or <keyword>.
make search also supports wildcards, such as:

	make search name="gtk*"

For information about contributing to FreeBSD ports, please see the Porter's
Handbook, available at:

	http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/

NOTE:  This tree will GROW significantly in size during normal usage!
The distribution tar files can and do accumulate in /usr/ports/distfiles,
and the individual ports will also use up lots of space in their work
subdirectories unless you remember to "make clean" after you're done
building a given port.  /usr/ports/distfiles can also be periodically
cleaned without ill-effect.

Description
No description provided
Readme 1.7 GiB
Languages
Makefile 59.7%
C 16.1%
Shell 7.2%
Roff 5%
C++ 3.7%
Other 7%