FreeBSD ports tree (read-only mirror)
2bdeafee66
down to user support flaws in the FreeBSD ports system. The flaw in question is related to the fact that dependencies are often "chained", which allows to simplify maintenance of ports with large number of implied dependencies (a la Evolution, Nautilus, you-name-it). Dependency chaining it's not a problem by itself, but the fact that when building or installing a port the system doesn't check chain integrity - it's only checks that dependencies explicitly specified in port's Makefile are satisfied, which opens wide window for various hard-trackable problems when one or more links in the middle of the chain missed. The idea behind the tool is quite simple - it should be executed right after main dependency checking procedure, two times for each build - check build-time chain before building the port (pre-pre-extract) and check run-time chain before installing the port (pre-pre-install). When executed, the tool checks integrity of the specified chain (build-time, run-time or both) and reports all errors, both fatal (dependency isn't installed) and non-fatal (dependency is installed, but different version). I've wrote this tool mostly to simplify maintenance of the GNOME ports, but it doesn't contain anything GNOME-specific, so that it could be used in the other parts of tree as well. As an example I've added GNOME_VALIDATE_DEPS_CHAIN knob into bsd.gnome.mk (off by default), which enables automatic chain validation for all ports that USE_GNOMELIBS. This is a bit hackish, because I've used pre-extract and pre-install targets - what we probably need is a generic way to plug various custom tasks specified in bsd.xxx.mk (where xxx is kde, gnome, python, etc.) into various parts of the build process (something like {pre,post}-pre-foo, {pre,post}-post-foo springs into my mind). The code is quite raw, so that I would appreciate any bug reports, patches, suggestions, constructive critiquie and so on. |
||
---|---|---|
accessibility/atk | ||
arabic | ||
archivers | ||
astro | ||
audio | ||
benchmarks | ||
biology | ||
cad | ||
chinese | ||
comms | ||
converters | ||
databases | ||
deskutils | ||
devel | ||
dns | ||
editors | ||
emulators | ||
finance | ||
french | ||
ftp | ||
games | ||
german | ||
graphics | ||
hebrew | ||
hungarian | ||
irc | ||
japanese | ||
java | ||
korean | ||
lang | ||
math | ||
mbone | ||
misc | ||
Mk | ||
multimedia | ||
net | ||
net-im | ||
net-mgmt | ||
net-p2p | ||
news | ||
palm | ||
picobsd | ||
polish | ||
ports-mgmt | ||
portuguese | ||
russian | ||
science | ||
security | ||
shells | ||
sysutils | ||
Templates | ||
textproc | ||
Tools | ||
ukrainian | ||
vietnamese | ||
www | ||
x11 | ||
x11-clocks | ||
x11-fm | ||
x11-fonts | ||
x11-servers | ||
x11-themes | ||
x11-toolkits | ||
x11-wm | ||
.cvsignore | ||
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. 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.