LEAFNODE_DATA_DIR, LEAFNODE_USER and LEAFNODE_GROUP, to be used by leafnode
to specify the data dir, the user and the group, defaulting to 'news'.
Note: the default is the same as for inn.
Pointed out by Georg Schwarz in mail to tech-pkg.
JAVA_WRAPPER_BIN.<wrapper-name>), in case it differs from the default.
For example, sablevm does not install a 'java' program with that name, so
adding 'java' to JAVA_WRAPPERS couldn't DTRT.
This file provides a framework to easily create wrappers to run Java
environments (either compilers or virtual machines) installed under
${PREFIX}/java/<implementation>. These wrappers hide the complexity
of having to modify the path, unlimit resources or to set a correct
CLASSPATH for the program to run.
Change that: if it's set to YES, require devel/patch. If building
devel/patch, set _OPSYS_GPATCH_REQD to NO, as otherwise we have a
circular dependency.
with gavan@NetBSD.org at pkgsrcCon.
Within the pkgsrc infrastructure, LOCALBASE has two different meanings:
(1) where the package being built should be installed, and
(2) where to find previously installed packages.
Most instances of case (2) should be converted to use EVAL_PREFIX,
but there are some cases where this is impossible. To resolve this,
we preserve LOCALBASE to mean (2) and we create a new variable
INSTALLATION_PREFIX to mean (1).
INSTALLATION_PREFIX is meant to be set some time before bsd.pkg.mk is
included, and provides the value for PREFIX if it's defined, e.g.
NO_MTREE= yes
INSTALLATION_PREFIX= /
.include "../../mk/bsd.pkg.mk"
This allows us to remove all cases where PREFIX is explicitly set in
the package Makefile, e.g. Java VM packages, qmail, etc.
USE_SUNPRO, USE_MIPSPRO variables would be removed. (According
to jlam@.)
mk/compiler.mk CVS:
----------------------------------------------------------------------
SETGIDGAME: specifies whether or not certain games are installed setgid
GAMEGRP: the group owning games if SETGIDGAME is set
GAMEOWN: the user owning games if SETFIDGAME is set
GAMEMODE: the mode to install games as
Use these to provide INSTALL_GAME (for example for PR pkg/25313), and
set them to meaningful values under NetBSD.
"yes"). So any packages that have old GNU configure script that
does not support --infodir option (while using INFO_FILES) can set
CONFIGURE_HAS_INFODIR=NO.
This was suggested by agc@ as a clearer definition.
requiring a specific compiler (most often those which use gcc-specific
hacks^wfeatures).
this allows users to define PKGSRC_COMPILER to multiple real compilers in
order to implement a compiler preference. for example,
PKGSRC_COMPILER="sunpro gcc" will use sunpro as the default compiler,
and fall back to gcc where a package is marked NOT_FOR_COMPILER=sunpro
or ONLY_FOR_COMPILER=gcc.
I have used this successfully to install over 300 info files
using INFO_DIR=share/info.
Also add new variable called NO_CONFIGURE_INFODIR (as suggested
by Greg Woods) because some autoconf-style configure scripts
don't know --infodir. (The alternative is to use HAS_CONFIGURE
and add the needed CONFIGURE_ARGS.)
Please note that the info tool may not find custom INFO_DIR
unless it is configure to know it. (I will update gtexinfo
for this, but if using native info you are on your own
if you customize this.)
(Not having this set caused various rpath related problems, as the compiler
was passed ' -rpath,/path' instead of '-Wl,-rpath,/path', leading to
a rpath of ",path", which of course wouldn't work.)
-traditional flag; you need to use "gcc -E" to get sane behavior.
Override sys.mk's definition of CPP in defs.Darwin.mk, and don't
re-override CPP in gcc.mk if ${OPSYS} == Darwin.