| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
on Solaris.
|
|
if an untested command fails (see sh(1), "-e errexit"). Do this by
changing lines that look like:
test expression && command
to
test ! expression || command
so that the statement list always returns 0. Also, back out revision
1.38 of pkgsrc/mk/install/install and modify the if-test to branch
correctly if +USERGROUP doesn't exist.
|
|
no user or group needs to be created. This fixes PR pkg/30849 by myself.
|
|
are specified, then don't create +USERGROUP, etc.
|
|
Based on suggestion by Matthias Drochner.
|
|
|
|
set must be selected, requested and reviewed by wiz:
PKG_OPTIONS_NONEMPTY_SETS
This is a list of names of sets of options. At
least one option from each set must be selected.
The options in each set are listed in
PKG_OPTIONS_SET.<setname>. Options from the sets
will be automatically added to PKG_SUPPORTED_OPTIONS.
|
|
|
|
is pkgsrc-supplied. In other cases, e.g. using the system tool,
falling back toS the system tool, etc., we should still create wrappers
and set "TOOL" variables.
|
|
|
|
Solaris.
fixes PR pkg/29608.
|
|
|
|
installed. That makes it easier to check if a specific package is listed
or not.
|
|
|
|
and mozilla. Backwards compatibilty is provided.
Reviewed by wiz.
|
|
for which you need to accept a license will display the necessary information.
ok gdt@.
|
|
"db2" as the "BUILDLINK_PACKAGES" variable. Drop the use of
_BDB_PKGBASE.*. This fixes the settings for BDBBASE and BDB_LIBS if
BDB_DEFAULT is "db2".
|
|
the linker, set _COMPILER_RPATH_FLAG accordingly. "-Wl," is removed by
the sunpro compiler wrapper where necessary.
fix comment for _LINKER_RPATH_FLAG while here.
this fixes, among other things, apache modules built with apxs.
|
|
install-rcd-${_script_} target; it gets created by mtree now.
|
|
RCD_SCRIPTS_EXAMPLEDIR has been fixed to this value for a while,
and because it ought not to be emitted by the print-PLIST target.
(Individual packages can't expect to be able to completely remove
this directory on deinstall, as it often has other packages' rc.d
scripts in it.)
|
|
too early for pkgsrc to adequately cope. In this case, imake-check.mk
was marking "imake" as a tool that was used to perform some tests.
This was causing xpkgwedge to be unnecessarily marked as a build
dependency since using imake in pkgsrc pretty much requires xpkgwedge.
However, in the case where we are running the "imake checks", we don't
need xpkgwedge around.
Solve this issue by marking all the tools in imake-check.mk with
":pkgsrc", and modify the xpkgwedge dependency test to not care about
"imake:pkgsrc".
|
|
actually increase readability by much.
|
|
djbdns, ezmlm, qmail.
|
|
clarifying from definition by example.
|
|
|
|
|
|
option is used. Noted by adrianp.
|
|
value passed via the shell environment to the GNU configure script for
each of the "GNU" variables names for the tool. It defaults to the full
path to the real tool so that these may be safely embedded in scripts
and config files.
One exception is the value for YACC when we use bison. In that case,
pass YACC="bison -y" to the configure script so that we will invoke
bison in yacc-compatibility mode.
|
|
|
|
|
|
|
|
outgoingip, qregex, realrcptto, sasl, starttls, syncdir, tinydns64,
tls, viruscan. Remove nullenvsender (obsolete).
|
|
|
|
line (path and arguments) needed to run the real tool.
Modify TOOLS_<TOOL> to hold only the path to the real tool.
Modify falcons-eye/Makefile and qt3-libs/Makefile.common to use
TOOLS_CMDLINE_YACC instead of TOOLS_YACC to that they'll use "bison -y".
|
|
reflect the possible variable contents.
|
|
|
|
tool. This variable is defined if <TOOL> is defined for that tool (see
tools/defaults.mk) and TOOLS_PATH.<tool> is set.
|
|
TOOLS_REAL_CMD.<tool> => TOOLS_PATH.<tool>
TOOLS_REAL_ARGS.<tool> => TOOLS_ARGS.<tool>
TOOLS_REAL_CMDLINE.<tool> => TOOLS_CMDLINE.<tool>
|
|
to another. This appears to fix whatever hidden bug a bit more
completely. "make show-var VARNAME=RM" in pkgsrc/x11/kdepim3 no longer
returns an empty value.
XXX I still have no idea why this "fixes" the problem. I can't seem to
XXX create a test case that exposes this problem.
|
|
Can't use an undefined value as an ARRAY reference at mk/bulk/post-build line 470.
In the case that no packages were broken, getBroken returns a hash
without the key "topten". When Perl tries to use that undefined value
as an array reference, it croaks.
|
|
logic in the tools framework.
|
|
tools listed in USE_TOOLS -- some of them are required by the pkgsrc
infrastructure in variable assignment statements that look like:
VARIABLE!= ${AWK} ...
These tools are actually *required* by pkgsrc to be installed on the
system before it can even work (bootstrap situation). For these tools,
only override the "TOOL" name representing the tool if we're really
using the pkgsrc version of the tool.
We accomplish this by adding a new :pkgsrc modifier that is appended
to these tools listed in USE_TOOLS. We also list these tools in
bsd.prefs.mk so that all packages pick them up fairly early on.
|
|
was empty.
XXX I have no idea why this fixes the problem.
|
|
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
|
