summaryrefslogtreecommitdiff
path: root/mk/tools/defaults.mk
AgeCommit message (Collapse)AuthorFilesLines
2009-07-08Add xzcat as a tool and update lzcat's TOOLS_DEPENDS to avoid conflicts.minskim1-1/+2
archivers/xz provides both lzcat and xzcat.
2009-02-05Drop tools/bootstrap.mk. It was mostly reundant as the bootstrapjoerg1-2/+1
components are correctly registered as dependencies. Move the remaining two exceptions into the corresponding platform files. XXX Both the strip and mkdir-sh are currently not registered
2008-11-15Add lzcat to the tools framework.minskim1-1/+2
lzcat will be used to decompress .lzma files.
2007-12-18Doing USE_TOOLS+=cmake in the configure stage is too late so move itmarkd1-1/+2
to tools. Also cmake wants cpack to exist in the same directory so toolise it and make cmake and cpack imply each other.
2007-12-12Add support for cmake as a tool (USE_TOOLS+=cmake) and for using it inmarkd1-1/+2
the configure stage of a build (by setting USE_CMAKE=yes).
2007-08-10Give rpm2pkg a standard variable name "RPM2PKG" and teach GNU configurejlam1-1/+3
scripts about "cat".
2007-06-19Create IDENT variable by default.joerg1-1/+2
2007-06-19Add bzip2 as tool. All platforms that had code to deal with bzcatjoerg1-1/+2
also get bzip2, the rest falls back to archivers/bzip2. OK jlam.
2006-10-15Teach how to unpack .gem files.minskim1-1/+2
2006-07-13Add DIGEST to the variables defined by default.jlam1-1/+2
2006-06-14Teach the tools framework about "openssl".jlam1-1/+2
2006-03-06Teach the tools framework how to supply a pkgsrc version of install-infojlam1-1/+2
if a native one isn't available. We ensure that the "install-info" tool in the tools directory is a no-op since the real info file registration is handled by the INSTALL/DEINSTALL script in pkgsrc/mk/pkginstall/install-info.
2006-03-05* Teach the tools framework how to supply the pkgsrc version ofjlam1-1/+2
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD when determining whether the native makeinfo can be used. * Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo. * Get rid of all the "split" argument deduction for makeinfo since the PLIST module already handles varying numbers of split info files correctly. NOTE: Platforms that have "makeinfo" in the base system should check that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are correct.
2006-01-21unzip uses UNZIP as a special environment variable to denote the optionsjlam1-2/+2
to pass to unzip. While this is stupid, it's still the reality, so we must not set UNZIP in the environment when calling unzip. Rename "UNZIP" to "UNZIP_CMD" to point to the path to the unzip binary.
2006-01-08Teach the tools framework about "gsoelim", which is the soelim tool fromjlam1-1/+2
a groff distribution.
2005-11-08Teach the tools framework about wish and tclsh, and set WISH and TCLSHjlam1-1/+5
accordingly for packages that need it.
2005-11-08Add "soelim", also part of groff if replacement is needed.tv1-1/+2
2005-11-04Teach the tools framework about "sleep" which can be provided by thejlam1-1/+2
sysutils/coreutils package.
2005-11-04Add a GNU variable for byacc so configure scripts will use YACC=byacc.jlam1-1/+2
2005-11-04Add 'printf' and 'byacc' variables corresponding to the new tools injlam1-1/+3
replace.mk.
2005-07-26Provide a "pod2man" tool used by some packages to build man pages.jlam1-1/+2
Based on suggestion by Matthias Drochner.
2005-07-15Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify ajlam1-2/+2
run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by makingjlam1-4/+4
PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable that specifies all of the tools we need to build/run the package.
2005-06-24Teach the tools framework about csh, and replace with tcsh if necessary.jlam1-1/+2
2005-06-24Remove unused variable _TOOLS_VARNAME.ldconfig.jlam1-2/+1
2005-06-24Support bash as a tool, so that packages containing bash scriptsminskim1-1/+2
(e.g. graphics/netpbm) use native bash if available.
2005-06-23Teach the tools framework about "diff".jlam1-1/+3
2005-06-17Pull out the LS and TR definitions from algae/Makefile and place themjlam1-1/+3
in tools/defaults.mk where they can be more widely used.
2005-06-17PERL_PATH is also a common GNU configure script variable for the path tojlam1-2/+2
the perl interpreter.
2005-06-11Remove unnecessary .undef lines after .for loops as the loop variablesjlam1-3/+1
are automatically undefined after the loop exits.
2005-06-10Force an autoconf "cache" override for tools that are likely to bejlam1-2/+5
shell builtins, e.g. echo, false, test, true, since those tools don't have a full path.
2005-06-07Add another common name for the GNU configure variable name used for thejlam1-2/+2
"env" tool.
2005-06-07Add a few more GNU configure variable names that are commonly used.jlam1-2/+7
Also, some configure scripts use "ENV" to represent the path to the "env" tool, which is probably bad since ENV has a special meaning to /bin/sh. To workaround this, set ac_cv_path_ENV.
2005-06-03Teach the tools framework about mktemp. Replace explicit tests forjlam1-1/+2
mktemp with USE_TOOLS+=mktemp in the samba packages.
2005-05-26Teach the tools framework about nroff.jlam1-1/+2
2005-05-23Work around brokenness in GNU configure scripts generated by autoconf-2.59ajlam1-3/+3
-- the checks for grep and egrep are broken because when passed GREP and EGREP in the environment, the script causes GREP and EGREP to be set to empty strings, which causes GNU configure scripts to hang or break. Pass the real paths to grep and egrep through using ac_cv_path_GREP and ac_cv_path_EGREP as well to avoid the brokenness. This fixes the build of textproc/gsed.
2005-05-22Don't add "INSTALL" to CONFIGURE_ENV as bsd.pkg.mk adds special valuesjlam1-2/+1
for INSTALL by itself during the configure stage. This fixes problems with GNU configure scripts using the wrong value of INSTALL.
2005-05-22Add a few more tools for GNU configure scripts: grep, env, xmkmf.jlam1-1/+4
2005-05-21For packages that use GNU configure scripts, pass the real commandjlam1-1/+32
paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-21Grammar 101 -- sentences should end in a period.jlam1-2/+2
2005-05-21Add TNF copyright to the new tools framework makefiles.jlam1-1/+36
2005-05-17Move perl handling into replace.mk. We now can specify USE_TOOLS+=perljlam1-1/+2
to note that we need the perl binary and the associated PERL5 and TOOLS_PERL5 variable definitions.
2005-05-15Asking the tools framework for "bison" now provides two distinct tools:jlam1-2/+2
"bison" and "bison-yacc". bison is just a symlink to the real bison, but "bison-yacc" provides a "yacc" in ${TOOLS_DIR} that does "bison -y". This allows the tools framework to provide everything that a package might look for when asking for "bison" and avoids relying on the bison being available in the PATH.
2005-05-14Consider ${TAR} differently from ${GTAR}. Currently, mark pkgsrc downjlam1-6/+2
as needing both (no impact since they're both satisfied by the tar binary installed by the bootstrap kit). There's some funniness in the extraction code where we check for pax or GNU tar that needs to be resolved. Remove the TAR=${GTAR} hack since it's no longer needed after these changes. XXX Later, a sweep needs to be made to see where we actually need GTAR XXX and where we only need TAR, probably triggered by whether we call it XXX with the "z" option or not. Packages that need GTAR should explicitly XXX add USE_TOOLS+=gtar to the package Makefile.
2005-05-14Temporarily define TAR here until I figure out a better way to dealjlam1-1/+6
with TAR vs. GTAR. This fixes pkg_install not being created with a tar command.
2005-05-14The mk/tools/defaults.mk is included by bsd.prefs.mk, so it must includejlam1-4/+4
other files without making assumptions about the location of the top of the pkgsrc tree. This fixes problems with running "make bulk-cache" in /usr/pkgsrc (PR pkg/30288).
2005-05-13Teach the new tools framework about lha, unrar, unzip, and unzoo andjlam1-1/+5
modify bsd.pkg.extract.mk to use them. As a side-effect, we stop hardcoding ${LOCALBASE} as the install prefix for these tools so this becomes more pkgviews-friendly.
2005-05-12Observe the following:jlam1-2/+5
VAR= a PTR= VAR ${PTR}?= b Given these definitions, ${VAR} == "b" (unintuitively). We can work around this by doing: VAR= a PTR= VAR .for _v_ in ${PTR} ${_v_}?= b .endfor In this case, ${VAR} == "a" (as expected). Use the second form of assignment in this changeset so that the expected behavior happens for the "TOOL" name variables. This fixes "recursively defined" errors for some of the "TOOL" variables when the pkgsrc tool replaces the system-supplied one.
2005-05-10Split out "strip" from the USE_TOOLS processing in replace.mk. Instead,jlam1-2/+1
we create a "strip" tool unconditionally, and make it either a no-op or the real thing depending on the whether we want unstripped files or not.
2005-05-10Make a distinction between the tools that pkgsrc needs and the toolsjlam1-4/+6
that a package needs. Tools that pkgsrc needs are listed in PKGSRC_USE_TOOLS, and tools that a package needs on top of that are listed in USE_TOOLS. Define "TOOL" variables, e.g. SED, AWK, MKDIR, etc. for each of the tools that pkgsrc needs, and "TOOLS_TOOL" variables, e.g. TOOLS_SED, TOOLS_AWK, TOOLS_MKDIR, etc. for each of the tools that a package needs. These variables contain the full command line to the real command and arguments needed to invoke the tool.