FreeBSD ports tree (read-only mirror)
5426e8d986
"not_found.html" stuff. (2) Add "MACHINE_ARCH?=i386" so those with a 2.x system have a fighting chance of getting ports-current to work. (3) Add new variable CONFIGURE_TARGET, defaulting to ${MACHINE_ARCH}--freebsd${OSREL}, which is tucked to the end of CONFIGURE_ARGS if GNU_CONFIGURE is defined. Reviewed by: various (4) Change MASTER_SITE_GNOME to match reality. Submitted by: Jeremy Lea <reg@shale.csir.co.za> and nectar (5) Change MASTER_SITE_SUBDIR handling so we won't be generating double slashes. Submitted by: The lord of distfiles himself (6) Add new variable FETCH_ENV which is the environment passed to FETCH, so people can define HTTP_PROXY or whatever the want without screwing up the case when FETCH_CMD is not fetch. PR: 2949 Submitted by: same |
||
---|---|---|
archivers | ||
astro | ||
audio | ||
benchmarks | ||
biology | ||
cad | ||
chinese | ||
comms | ||
converters | ||
databases | ||
deskutils | ||
devel | ||
dns | ||
editors | ||
emulators | ||
finance | ||
ftp | ||
games | ||
german | ||
graphics | ||
irc | ||
japanese | ||
java | ||
korean | ||
lang | ||
math | ||
mbone | ||
misc | ||
Mk | ||
multimedia | ||
net | ||
net-im | ||
net-mgmt | ||
news | ||
palm | ||
ports-mgmt | ||
russian | ||
science | ||
security | ||
shells | ||
sysutils | ||
Templates | ||
textproc | ||
Tools | ||
vietnamese | ||
www | ||
x11 | ||
x11-clocks | ||
x11-fm | ||
x11-fonts | ||
x11-servers | ||
x11-themes | ||
x11-toolkits | ||
x11-wm | ||
.cvsignore | ||
INDEX | ||
LEGAL | ||
Makefile | ||
README | ||
YEAR2000 |
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 which is available from: file://localhost/usr/share/doc/handbook/handbook.html (if you installed the doc distribution on your machine) Or: http://www.freebsd.org/handbook/handbook.html for the latest official version from FreeBSD-current. The section "The Ports Collection" will tell you how to use the ports and packages and the "Porting Applications" section describes how one can contribute to the ports collection. If you would like to search for a given port, you can do so easily by saying: make search key="<keyword>" Which will generate a list of all ports matching <keyword>. NOTE: This tree can 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, though if you don't have the original distribution tarball(s) for something on CDROM then you will need to pull it all over your network connection again if you ever try to build the associated port.