summaryrefslogtreecommitdiff
path: root/www/tidy
diff options
context:
space:
mode:
authorjlam <jlam@pkgsrc.org>2002-09-27 09:22:58 +0000
committerjlam <jlam@pkgsrc.org>2002-09-27 09:22:58 +0000
commit84cb9a37e990b3ecf2ba972569e5ea5452219f63 (patch)
treeab23a40fa63327e998107315ef50b72d2aa50d51 /www/tidy
parentb1cedbc5e22f8bfe2c4d1e545396da5e8d2f2680 (diff)
downloadpkgsrc-84cb9a37e990b3ecf2ba972569e5ea5452219f63.tar.gz
Create a new variable USE_X11_LINKS that controls whether packages that
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.
Diffstat (limited to 'www/tidy')
0 files changed, 0 insertions, 0 deletions