Personal patches
a3bcf12a10
(default: IS_DEPENDED?=install) target on the depended port, call DEPENDS_TARGET (default: install) from the depending port. Other than being more flexible (some ports don't require the dependency to be fully installed: see ghostscript4), this seems like a more natural thing to do. (I never understood the convoluted logic that was used before.) By building packages with "DEPENDS_TARGET=package", I can avoid file-sharing problems (like gs3 binary going into the gs4 package). (2) Add new variable PATCH_SITE_SUBDIR and separate it from MASTER_SITE_SUBDIR. Fixes linuxls port and is a correct thing to do anyway. Initially suggested and reviewed by: fenner (3) Add new variable MASTER_SITE_LOCAL for local ports. Defaults to LOCAL_PORTS subdir on ftp.freebsd.org's distfiles dir. Submitted by: jkh |
||
---|---|---|
archivers | ||
astro | ||
audio | ||
benchmarks | ||
cad | ||
chinese | ||
comms | ||
converters | ||
databases | ||
deskutils | ||
devel | ||
dns/p5-Net-DNS | ||
editors | ||
emulators | ||
finance/p5-Business-CreditCard | ||
ftp | ||
games | ||
graphics | ||
irc | ||
japanese | ||
java | ||
korean | ||
lang | ||
math | ||
mbone | ||
misc | ||
Mk | ||
multimedia | ||
net | ||
net-mgmt | ||
news | ||
ports-mgmt/pib | ||
russian | ||
science/felt | ||
security | ||
shells | ||
sysutils | ||
Templates | ||
textproc | ||
vietnamese | ||
www | ||
x11 | ||
x11-clocks | ||
x11-fm | ||
x11-fonts | ||
x11-servers | ||
x11-toolkits | ||
x11-wm | ||
INDEX | ||
LEGAL | ||
Makefile | ||
README |
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. 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.