use buildlink2 and set USE_X11 will use x11-links, or if they will simply symlink the X11 files directly into ${BUILDLINK_DIR}. If USE_X11_LINKS is "YES" (the default), then x11-links is used. If USE_X11_LINKS is "NO", then the X11 files are symlinked directly. There is a choice here between speed and flexibility. Using x11-links is faster since you don't need to spend time symlinking all of the X11 files into ${BUILDLINK_DIR}. However, if you update your X11 installation, then the x11-links package will likely be out-of-date. Conversely, directly symlinking the X11 files will protect you from changes in your X11 installation when you update, but there is a (small) time penalty to have to do it for every package that uses X11. |
||
---|---|---|
.. | ||
bsdpak | ||
cdpack | ||
createbuildlink | ||
digest | ||
gensolpkg | ||
pax | ||
pkg_comp | ||
pkg_install | ||
pkg_tarup | ||
pkgchk | ||
pkgconflict | ||
pkgdep | ||
pkgdiff | ||
pkglint | ||
pkgmanpages | ||
pkgsurvey | ||
port2pkg | ||
rpm2pkg | ||
shlock | ||
url2pkg | ||
x11-links | ||
xpkgwedge | ||
Makefile |