Each word of UNLIMIT_RESOURCES is supposed to be a knob on
ULIMIT_CMD_<word> variable which value if defined is added to _ULIMIT_CMD.
The ULIMIT_CMD_* variables are set per $OPSYS in defs.*.mk and are overridable
by the user.
Solaris' default value of ULIMIT_CMD_memorysize adjusted as suggested in PR
pkg/18087 by Jonathan Perkin <sketch@rd.bbc.co.uk>.
if the interactive stage is "fetch", since there will be no ${WRKDIR} at
that time.
Instead, since ${INTERACTIVE_COOKIE}s are only used in bulk builds, create
them in the package directory, along with the related .broken.`hostname`
file.
* move redundant sed expression into variable to only maintain it once
* properly catch grep return code in *both* cases (makes substitution
of pkg variables in @dirrm statements / directory names work)
contents.
* Each PKG_JVM needs its own special _JAVA_PREFIX_DEFAULT hardcoded as
there's no way to discern the subdirectory of ${LOCALBASE}/java in which
the PKG_JVM is installed.
* If PKG_JVM == "sun-jdk", allow either sun-jdk13 or sun-jdk14 to be used,
preferring whichever one is already installed, but otherwise using the
best default for a given platform.
(instead of "build"). The rationale is that USE_JAVA= is "bigger" than
USE_JAVA=run in the sense that the former adds another dependency. For
packages that don't need the extra dependency, we can trim it off by
setting USE_JAVA more thoughtfully.
an optional value of "build" to represent that the package only wants a
build dependency on perl.
* Add a new public variable "PERL5_PKGSRCDIR" that is either
"../../lang/perl58" or "../../lang/perl5" depending on whether we need
perl>=5.8.0 or not.
Example:
CONFIG_GUESS_OVERRIDE= ${WRKSRC}/config.guess
CONFIG_SUB_OVERRIDE= ${WRKSRC}/config.sub
Just before the bulk of the "configure" phase, the named files will be
replaced with symlinks to their canonical pkgsrc versions in
pkgsrc/mk/gnu-config.
/usr/bin/gzcat nor ${LOCALBASE}/bin/gzip exist.
required for Solaris systems which do not include gzcat in the base
system.
sanity checked by Stoned Elipot <seb@netbsd.org>.
batch mode, into a separate target.
Call that target if we're in batch mode.
Modify the check for distfiles code to do a loop for all the
distfiles, and only print the message once at the end if the files
aren't present, and BATCH is defined.
Only check for distfiles' explicit presence if BATCH is defined.
definition.
INTERACTIVE_STAGE can take any of the values: fetch, configure, build and
install
Multiple values are allowed: e.g. INTERACTIVE_STAGE= configure install
Explain INTERACTIVE_STAGE and its use in documentation.
Patches provided by Chris Pinnock (cjep@netbsd.org).
Note: it was already as part of CONFIGURE_ENV value, this change only makes
it more "readable" IMHO.
Remove explicit addition of PKG_SYSCONFDIR to BUILD_DEFS in a couple of
Makefiles.
--prefix option passed to a GNU configure script. It defaults to
${PREFIX}. This should help simplify the packages out there that avoid
setting GNU_CONFIGURE=yes because they need a custom --prefix option.
(1) Admins want to create users/groups on their own (pkg/17183).
(2) Admins don't want packages to setup an initial configuration.
The bsd.pkg.install.mk-generated INSTALL/DEINSTALL scripts have been
modified to check certain PKG_* environment variables to tune their
behaviour. This works whether installing from "make install" or from a
binary package.
PKG_CREATE_USERGROUP indicates whether the INSTALL script should
automatically add any needed users/groups to the system using
useradd/groupadd. It is either YES or NO, and defaults to YES.
PKG_CONFIG indicates whether the INSTALL/DEINSTALL scripts should do
automatic config file and directory handling, or if it should
merely inform the admin of the list of required files and
directories needed to use the package. It is either YES or NO,
and defaults to YES.
The make(1) variable INSTALL_RCD_SCRIPTS is removed. The package rc.d
script is now handled like other config files for the package, and is
copied into place if PKG_CONFIG=YES.
The default values above reflect the current behaviour. Setting
PKG_CREATE_USERGROUP=NO solves problem (1), and setting PKG_CONFIG=NO
solves problem (2).
To simply matters for users installing directly from pkgsrc, these
variables may also be defined in /etc/mk.conf, but behaviour at deinstall
time may be surprising. It is *HIGHLY* recommended that these values be
set in the shell environment instead.
which the basesrc USE_KERBEROS variable. Discussed on packages@
This fixes PR#17182 from Takahiro Kambe. The problem was pointed out by
FUKAUMI Naoki on a Japanese NetBSD mailing list.
