Make it clear that it's a bad idea to try having multiple (different)
settings for LOCALBASE etc., noted by Paul Hoffman <phoffman@proper.com>
This commit is contained in:
parent
c773fdc575
commit
e5f918615f
1 changed files with 10 additions and 1 deletions
11
Packages.txt
11
Packages.txt
|
@ -1,4 +1,4 @@
|
|||
# $NetBSD: Packages.txt,v 1.132 2001/01/04 15:10:17 agc Exp $
|
||||
# $NetBSD: Packages.txt,v 1.133 2001/01/06 03:10:02 hubertf Exp $
|
||||
###########################################################################
|
||||
|
||||
==========================
|
||||
|
@ -259,6 +259,15 @@ manually, you can use the the "bin-install" target, which will
|
|||
install a binary package - if available - via pkg_add, and do a "make
|
||||
package" else.
|
||||
|
||||
A final word of warning: If you setup a system that has a non-standard
|
||||
setting for LOCALBASE (or X11BASE, for that matter), be sure to set that
|
||||
before any packages are installed, as you can not use several directories
|
||||
for the same purpose. Doing so will result in pkgsrc not being able to
|
||||
properly detect your installed packages, and fail miserably. Note also that
|
||||
precompiled binary packages are usually built with the default LOCALBASE of
|
||||
/usr/pkg, and that you should *not* install any if you use a non-standard
|
||||
LOCALBASE.
|
||||
|
||||
|
||||
3 Making precompiled packages
|
||||
=============================
|
||||
|
|
Loading…
Reference in a new issue