I've add this port as a 'new' port, even though we already have
ports/irc/keitairc, keitairc 1.x. Because...
- keitairc 2.x is a _complete_ rewrite of keitairc 1.x
keitairc 1.x is just a single perl script, but keitairc 2.x
is composed of a script, Keitairc perl module, templates, etc.
Also there is no configuration file compability between 1.x and 2.x.
- keitairc 2.x port is a _complete_ rewrite of keitairc 1.x
Since the application structure is changed, I have to write
a new port for 2.x, instead of _modify_ 1.x port.
Tested by: nork
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.