summaryrefslogtreecommitdiff
path: root/mk/bsd.pkg.use.mk
AgeCommit message (Collapse)AuthorFilesLines
2017-03-05Fix path to cross-libtool-base in TOOL_DEPENDS+= for crossbuildingkamil1-2/+2
2017-01-18Coorect version of libtool to current one.taca1-2/+2
2017-01-17Bump LIBTOOL_REQD, newer version needed for cwrappers.wiz1-2/+2
PR 51826.
2016-11-10Handle optional ctfmerge/ctfconvert presence on NetBSD by explicitlyjoerg1-1/+4
passing down NOCTF when they don't exist.
2016-06-19Get rid of INSTALLATION_PREFIX.wiz1-5/+1
2016-06-19Remove support for USE_CROSSBASE.wiz1-3/+1
2015-07-04Remove USE_X11BASE and X11PREFIX.joerg1-8/+1
2015-05-04Drop _LIBTOOL and _SHLIBTOOL and make LIBTOOL and SHLIBTOOL point to thejoerg1-8/+4
wrapped version by full path. This fixes some cases where the wrappers have been bypassed. lang/lua52 triggered the investigation as it failed to link against libreadline, which should have been translated to libedit. Tested by jperkin and myself with full bulk builds.
2014-12-30Remove pkg_views support, second part: infrastructure.wiz1-13/+5
2014-10-01Remove mk glue for devel/nbitools.joerg1-5/+2
2013-09-09Only add HAVE_LLVM / HAVE_GCC if they are already set.joerg1-2/+8
2013-09-08Pass down HAVE_LLVM and HAVE_GCC.joerg1-2/+2
2013-05-10check defined before using USE_LANGUAGES as condition.obache1-2/+3
2013-05-09Split BUILD_DEPENDS into TOOL_DEPENDS and BUILD_DEPENDS in mk/.riastradh1-2/+15
Build depends are target packages that are needed at build-time for, e.g., static libraries to link against, header files to include, &c. Tool depends are native packages that are needed at build-time for, e.g., compilers/linkers/&c. to run. ok agc
2013-05-09Split Fortran support from devel/libtool-base into a separate packagejoerg1-1/+10
devel/libtool-fortran. If USE_LIBTOOL is present and Fortran is in USE_LANGUAGES, include the new package.
2012-03-19Drop imake-check logic from X11 components' builtin.mk.joerg1-12/+1
Always use xorg-cf-files and imake from pkgsrc, replacing xpkgwedge. Always install man pages, not cat pages when using imake. Unify the various imake PLIST variables in preparation for dropping. Adjust xbattbar for the new expectations.
2009-12-20Fix libtool under OS X: require a fixed version of f2c, and thus bumpjmmv1-2/+2
PKGREVISION of libtool to 3 and require it as a dependency.
2009-12-16Force libtool 2.2 on all platforms.joerg1-2/+2
2009-07-22Remove USE_DIRS infrastructure support and support packages.wiz1-8/+1
See http://mail-index.netbsd.org/pkgsrc-changes/2009/07/22/msg026834.html.
2008-05-16If we have USE_BSD_MAKEFILE, pass down INSTALL=${TOOLS_INSTALL:Q} in thetnn1-2/+2
environment. Otherwise BSD style packages will use the install(1) which bootstrap-mk-files' sys.mk picked, rather than the one from TOOLS_PLATFORM.install (which may be specified by the user in mk.conf).
2008-02-07Get rid of USE_TOOLS+=nroff in the USE_BSD_MAKEFILE case.tnn1-2/+1
Just because a package has BSD style Makefile doesn't mean it has manpages. A sweep of packages with USE_BSD_MAKEFILE=yes is forthcoming; USE_TOOLS+=groff nroff will be added where appropriate.
2007-11-30Documented USE_IMAKE.rillig1-1/+9
2007-10-17Made the .include lines simpler.rillig1-3/+3
2007-07-02Remove USE_MTREE support. Keep one copy (the NetBSD version) forjoerg1-6/+3
the purpose of print-PLIST in plist/common-dirs.mtree. Discussed with wiz@, no objections on tech-pkg@.
2007-03-02Make MTREE_FILE and MTREE_ARGS internal by prefixing them with '_'.wiz1-2/+2
They are not supposed to be set by the user.
2007-02-10Replaced the deprecated PKG_SKIP_REASON with PKG_FAIL_REASON.rillig1-2/+2
2007-01-22Reverted the change between 1.37 and 1.38.rillig1-2/+1
MANPATH cannot be overridden so easily to make it right for imake Packages. Noticed by Dan.
2007-01-07Added the variable USE_BSD_MAKEFILE.rillig1-4/+13
2007-01-06Fixed PKGMANDIR for all packages using Imake.rillig1-1/+2
2006-12-20For modular Xorg disable xpkgwedge (will be made a hard error later).joerg1-2/+4
Don't add ${X11BASE}/bin to PATH, don't include mk/x11.buildlink3.mk when USE_X11BASE is set and don't use BUILDLINK_X11_DIR and related magic. OKed by wiz@
2006-07-07No need to define LIBTOOL_OVERRIDE explicitly since libtool-override.mkjlam1-2/+1
will search for libtool scripts up to ${OVERRIDE_DIRDEPTH} below ${WRKSRC} already.
2006-07-05Teach the tools framework about the following new tools:jlam1-2/+6
itools, intltool, diff3, sdiff, msgmerge * Adding USE_TOOLS+=itools to a package Makefile will cause the tool-directory versions of imake, makedepend, mkdirhier and xmkmf to point to the ones from the devel/nbitools package. This change will remove the need for nbitools/buildlink3.mk, which currently does a bit of hackery to force the "right" imake tools to be used by packages that need it. * Adding USE_TOOLS+=intltool to a package Makefile will cause the local versions of intltool-* inside ${WRKSRC} to be replaced by copies from the textproc/intltool package. If "intltool" is not specified as a tool, then we create "broken" intltool-* tools in the tools directory to help highlight hidden dependencies on the intltool package. In addition, modify the tools framework so that if "perl" is not specified as a tool, then we create a "broken" perl tool in the tools directory for the same reason as for "intltool". These two changes together will remove the need for intltools/buildlink3.mk and should also catch all cases where the sources' intltools may have been silently used because perl was found on the system. * Adding USE_TOOLS+=diff3, USE_TOOLS+=sdiff, or USE_TOOLS+=msgmerge to a package Makefile will cause the corresponding tool to be pulled into the tools directory. These are convenience tools to help simplify dependencies for some packages.
2006-06-03First pass at implementing support for package system flavors otherjlam1-4/+1
than pkgsrc's current one. This is an important lead-up to any project that redesigns the pkg_* tools in that it doesn't tie us to past design (mis)choices. This commit mostly deals with rearranging code, although there was a considerable amount of rewriting done in cases where I thought the code was somewhat messy and was difficult to understand. The design I chose for supporting multiple package system flavors is that the various depends, install, package, etc. modules would define default targets and variables that may be overridden in files from pkgsrc/mk/flavor/${PKG_FLAVOR}. The default targets would do the sensible thing of doing nothing, and pkgsrc infrastructure would rely on the appropriate things to be defined in pkgsrc/mk/flavor to do the real work. The pkgsrc/mk/flavor directory contains subdirectories corresponding to each package system flavor that we support. Currently, I only have "pkg" which represents the current pkgsrc-native package flavor. I've separated out most of the code where we make assumptions about the package system flavor, mostly either because we directly use the pkg_* tools, or we make assumptions about the package meta-data directory, or we directly manipulate the package meta-data files, and placed it into pkgsrc/mk/flavor/pkg. There are several new modules that have been refactored out of bsd.pkg.mk as part of these changes: check, depends, install, package, and update. Each of these modules has been slimmed down by rewriting them to avoid some recursive make calls. I've also religiously documented which targets are "public" and which are "private" so that users won't rely on reaching into pkgsrc innards to call a private target. The "depends" module is a complete overhaul of the way that we handle dependencies. There is now a separate "depends" phase that occurs before the "extract" phase where dependencies are installed. This differs from the old way where dependencies were installed just before extraction occurred. The reduce-depends.mk file is now replaced by a script that is invoked only once during the depends phase and is used to generate a cookie file that holds the full set of reduced dependencies. It is now possible to type "make depends" in a package directory and all missing dependencies will be installed. Future work on this project include: * Resolve the workflow design in anticipation of future work on staged installations where "package" conceptually happens before "install". * Rewrite the buildlink3 framework to not assume the use of the pkgsrc pkg_* tools. * Rewrite the pkginstall framework to provide a standard pkg_* tool to perform the actions, and allowing a purely declarative file per package to describe what actions need to be taken at install or deinstall time. * Implement support for the SVR4 package flavor. This will be proof that the appropriate abstractions are in place to allow using a completely different set of package management tools.
2006-05-25No package is using USE_RMAN any longer, remove it.wiz1-13/+1
2006-04-13BUILD_USE_MSGFMT and USE_MSGFMT_PLURALS are obsolete. Replace withjlam1-7/+1
USE_TOOLS+=msgfmt.
2006-04-13Overhaul the way packages can ask for "msgfmt". If a package needsjlam1-4/+3
msgfmt, then it should set the following in the package Makefile: USE_TOOLS+= msgfmt To deal with message files that use the "msgid_plural" statement, which isn't supported in NetBSD<=3.x and also in gettext<=0.10.35, we determine if the built-in "msgfmt" is sufficiently new enough to understand "msgid_plural". If it isn't, then we use the msgfmt.sh script to transform the msgid_plural statements to an equivalent construct that's understood by older msgfmt tools. The msgfmt.sh script is a straightforward translation of the original perl script msgfmt.pl script by Julio M. Merino Vidal into shell and awk, which are more lightweight dependencies than perl. We remove the USE_MSGFMT_PLURALS bits in gettext-lib/builtin.mk as they are made obsolete by the new code in mk/tools/msgfmt.mk. BUILD_USE_MSGFMT is still supported but will be removed in a separate commit.
2006-03-11BUILD_DEPENDS on gettext-tools not gettext for BUILD_USES_MSGFMT.reed1-2/+2
2006-03-09Reimplement the info-file handling so that we use an +INFO_FILESjlam1-9/+1
scriptlet to manage the info-file registration. The new scriptlet's template is install/info-files. Remove obsolete texinfo.mk and install/install-info. No changes to package Makefiles are necessary -- the re-implementation is internal to pkgsrc infrastructure.
2006-03-05* Teach the tools framework how to supply the pkgsrc version ofjlam1-4/+3
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-12Require xpkgwedge 1.15.joerg1-2/+2
2006-01-12Don't ever depend on xpkgwedge if we're building xpkgwedge.jlam1-1/+2
2005-12-05Applied all quoting fixes found by "pkglint --autofix".rillig1-15/+15
2005-12-04Add IMAKE_GAMEMAN_SUFFIX and IMAKE_GAMEMAN_DIR to allow PLISTsjoerg1-1/+3
to pick up the correct locations. XXX Default values are guessed, x11/xsnow can be used for testing
2005-09-21Bump LIBTOOL_REQD to 1.5.18nb5. This pulls in the -avoid-version fix fortv1-2/+2
some platforms, which includes all non-ELFs and many ELF-like platforms (that still use a.out naming conventions). Since a branch is coming, bump the version in a blanket rather than per platform.
2005-07-19Tools that are marked with ":pkgsrc" are needed very early on, probablyjlam1-2/+3
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".
2005-06-23Clean up some clutter in pkgsrc/mk: move the ${OPSYS}.*.dist mtreejlam1-2/+2
files into mk/platform, where they now live with the ${OPSYS}.mk files.
2005-06-14Require xpkgwedge>=1.14 so that the correct make is always invoked onjlam1-2/+2
Solaris and Linux, regardless of whether we use the same make to build the software or not.
2005-06-14We need xpkgwedge whenever we use imake.jlam1-2/+4
2005-06-14Require xpkgwedge>=1.13 when used as a build dependency so that thejlam1-2/+2
correct make(1) program is invoked by pkgxmkmf.
2005-06-14We only need to set USE_X11BASE, run install.man, and override thejlam1-3/+6
compiler (CC/CXX) if we're actually using imake to generate Makefiles for building and installing software. This fixes errors in various KDE-3.x packages that use imake for other purposes.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-17 22:33:17 +0000