kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/mk/bsd.pkg.mk

1045 lines
32 KiB
Makefile
Raw Normal View History

Remove line noting that "this file was derived from bsd.ports.mk". The contents of this file are no longer remotedly related to bsd.ports.mk, and pkgsrc's heritage from ports is documented elsewhere.
2006-07-13 16:04:41 +02:00
# $NetBSD: bsd.pkg.mk,v 1.1870 2006/07/13 14:04:41 jlam Exp $
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
#
move documentation to packages.7. also, remove ts=4 crap.
1998-06-05 14:45:53 +02:00
# This file is in the public domain.
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
#
Merge down some more visual cleanup from tv-derecurse to reduce divergence. Part of this, introduce bsd.pkg.use.mk, where the Special Logic invoked by various pkgsrc-wide USE_* variables will be migrated/consolidated.
2005-02-11 16:55:13 +01:00
# Please see the pkgsrc/doc/guide manual for details on the
# variables used in this make file template.
#
Update the comments to reflect the current default workflow.
2006-07-08 04:16:33 +02:00
# Default sequence for "all" is:
#
* Add a new stage "bootstrap-depends" that happens before all other stages, and that installs dependencies listed in BOOTSTRAP_DEPENDS. The bootstrap-depends step works just like the normal depends step and honors the value of DEPENDS_TARGET. It's now possible to add dependencies solely to facilitate fetching the distfiles, e.g. BOOTSTRAP_DEPENDS+= curl-[0-9]*:../../www/curl * Teach the tools framework about ":bootstrap" as a tools modifier which indicates the tool should be added as a dependency via BOOTSTRAP_DEPENDS. * Add "digest" to the tools framework. * Use USE_TOOLS+=digest:bootstrap to force pkgsrc to install digest before anything else. Get rid of unused "uptodate-digest" target and related digest version-checking code. * Finish the refactoring work: split checksum-related code out of bsd.pkg.mk and into pkgsrc/mk/checksum and replace the "checksum" target command list with a script that does all the real work. * Make DIGEST_ALGORITHMS and PATCH_DIGEST_ALGORITHM into private variables by prepending them with an underscore. Also, rename _PATCH_DIGEST_ALGORITHM to _PATCH_DIGEST_ALGORITHMS and adjust the makepatchsum target to allow that variable to contain a list of algorithms, all of which are used when creating the patch checksums for ${DISTINFO_FILE}.
2006-07-13 16:02:34 +02:00
# bootstrap-depends
# fetch
# checksum
# depends
# tools
# extract
# patch
# wrapper
# configure
# build
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
#
Merge down some more visual cleanup from tv-derecurse to reduce divergence. Part of this, introduce bsd.pkg.use.mk, where the Special Logic invoked by various pkgsrc-wide USE_* variables will be migrated/consolidated.
2005-02-11 16:55:13 +01:00
############################################################################
# Include any preferences, if not already included, and common definitions
############################################################################
Fix previous... instead of moving bsd.pkg.barrier.mk down below .MAIN, move .MAIN all the way to the top of the file. bsd.pkg.barrier.mk (currently) needs to be included before bsd.wrapper.mk since it defines _BARRIER_COOKIE, which is expanded and used in place within bsd.wrapper.mk. This makes the "wrapper" phase run again.
2006-07-06 18:58:17 +02:00
.MAIN: all
Implement some parts of proposals posted to tech-pkg: - Define OS_VERSION in bsd.prefs.mk (...if not already defined). Previously was only set in a conditional block in bsd.pkg.mk. - Define new values, MACHINE_PLATFORM and MACHINE_GNU_PLATFORM, which default to ${OPSYS}-${OS_VERSION}-${MACHINE_ARCH} and ${LOWER_OPSYS}-${LOWER_VENDOR}-${LOWER_ARCH} respectively. (Probably should nuke LOWER_ARCH and rename LOWER_VENDOR to something like MACHINE_GNU_VENDOR.) - Use ${MACHINE_GNU_PLATFORM} as the argument to `--host' in GNU_CONFIGURE packages. - Allow for ONLY_FOR_PLATFORM and NOT_FOR_PLATFORM, lists of patterns in csh(1) glob style which are matched against MACHINE_PLATFORM above and take the place of {ONLY,NOT}_FOR_{ARCHS,OPSYS}. (For now, until all pkgs are converted, provide backwards compatibility.) *Both* may be defined, in which case NOT_FOR_PLATFORM takes precedence. - Also do some significant aesthetic cleanup, based on the idea `define platform-specific overrides first, then define a generic case with the ?= operator'. Lots more of this to do yet.
1999-05-24 20:42:00 +02:00
.include "../../mk/bsd.prefs.mk"
Move some variable definitions out of bsd.prefs.mk and back into bsd.pkg.mk. They didn't actually need to be defined in bsd.prefs.mk, just somewhere before the "main" bsd.<phase>.mk files were included. This moves some conditional (?=) definitions back into bsd.pkg.mk so they won't conflict with any conditional definitions in package Makefiles. This should fix the "checksum" problems in lang/php-gd as noted here: http://mail-index.netbsd.org/pkgsrc-users/2006/06/05/0012.html where EXTRACT_SUFX had the wrong value due to the order in while *.mk files were included.
2006-06-06 17:28:51 +02:00
.include "${PKGSRCDIR}/mk/flavor/bsd.flavor-vars.mk"
.include "${PKGSRCDIR}/mk/check/bsd.check-vars.mk"
.include "${PKGSRCDIR}/mk/depends/bsd.depends-vars.mk"
.include "${PKGSRCDIR}/mk/fetch/bsd.fetch-vars.mk"
* Add a new stage "bootstrap-depends" that happens before all other stages, and that installs dependencies listed in BOOTSTRAP_DEPENDS. The bootstrap-depends step works just like the normal depends step and honors the value of DEPENDS_TARGET. It's now possible to add dependencies solely to facilitate fetching the distfiles, e.g. BOOTSTRAP_DEPENDS+= curl-[0-9]*:../../www/curl * Teach the tools framework about ":bootstrap" as a tools modifier which indicates the tool should be added as a dependency via BOOTSTRAP_DEPENDS. * Add "digest" to the tools framework. * Use USE_TOOLS+=digest:bootstrap to force pkgsrc to install digest before anything else. Get rid of unused "uptodate-digest" target and related digest version-checking code. * Finish the refactoring work: split checksum-related code out of bsd.pkg.mk and into pkgsrc/mk/checksum and replace the "checksum" target command list with a script that does all the real work. * Make DIGEST_ALGORITHMS and PATCH_DIGEST_ALGORITHM into private variables by prepending them with an underscore. Also, rename _PATCH_DIGEST_ALGORITHM to _PATCH_DIGEST_ALGORITHMS and adjust the makepatchsum target to allow that variable to contain a list of algorithms, all of which are used when creating the patch checksums for ${DISTINFO_FILE}.
2006-07-13 16:02:34 +02:00
.include "${PKGSRCDIR}/mk/checksum/bsd.checksum-vars.mk"
Move some variable definitions out of bsd.prefs.mk and back into bsd.pkg.mk. They didn't actually need to be defined in bsd.prefs.mk, just somewhere before the "main" bsd.<phase>.mk files were included. This moves some conditional (?=) definitions back into bsd.pkg.mk so they won't conflict with any conditional definitions in package Makefiles. This should fix the "checksum" problems in lang/php-gd as noted here: http://mail-index.netbsd.org/pkgsrc-users/2006/06/05/0012.html where EXTRACT_SUFX had the wrong value due to the order in while *.mk files were included.
2006-06-06 17:28:51 +02:00
.include "${PKGSRCDIR}/mk/extract/bsd.extract-vars.mk"
.include "${PKGSRCDIR}/mk/patch/bsd.patch-vars.mk"
Refactor configure, build, test and wrapper phases out of bsd.pkg.mk and into their own directories. Also do some cleanups with build/_build and pkginstall -- we get rid of _build and simply run pkginstall as part of the "build" target. Introduce a new mechanism to handle varying directory depths under ${WRKSRC} in which we find files to override, e.g. configure, config.*, libtool, etc. OVERRIDE_DIRDEPTH is a package-settable variable that specifies how far under ${WRKSRC} the various targets should look, and it defaults to "2". We preserve the meaning of the various *_OVERRIDE variables, so if they are defined, then their values supersede the OVERRIDE_DIRDEPTH mechanism. devel/tla will need to specially set OVERRIDE_DIRDEPTH to 3 (see log for revision 1.1857 for bsd.pkg.mk -- to be done in a separate commit.
2006-07-05 08:09:15 +02:00
.include "${PKGSRCDIR}/mk/configure/bsd.configure-vars.mk"
.include "${PKGSRCDIR}/mk/build/bsd.build-vars.mk"
Move some variable definitions out of bsd.prefs.mk and back into bsd.pkg.mk. They didn't actually need to be defined in bsd.prefs.mk, just somewhere before the "main" bsd.<phase>.mk files were included. This moves some conditional (?=) definitions back into bsd.pkg.mk so they won't conflict with any conditional definitions in package Makefiles. This should fix the "checksum" problems in lang/php-gd as noted here: http://mail-index.netbsd.org/pkgsrc-users/2006/06/05/0012.html where EXTRACT_SUFX had the wrong value due to the order in while *.mk files were included.
2006-06-06 17:28:51 +02:00
.include "${PKGSRCDIR}/mk/install/bsd.install-vars.mk"
* Add a new stage "bootstrap-depends" that happens before all other stages, and that installs dependencies listed in BOOTSTRAP_DEPENDS. The bootstrap-depends step works just like the normal depends step and honors the value of DEPENDS_TARGET. It's now possible to add dependencies solely to facilitate fetching the distfiles, e.g. BOOTSTRAP_DEPENDS+= curl-[0-9]*:../../www/curl * Teach the tools framework about ":bootstrap" as a tools modifier which indicates the tool should be added as a dependency via BOOTSTRAP_DEPENDS. * Add "digest" to the tools framework. * Use USE_TOOLS+=digest:bootstrap to force pkgsrc to install digest before anything else. Get rid of unused "uptodate-digest" target and related digest version-checking code. * Finish the refactoring work: split checksum-related code out of bsd.pkg.mk and into pkgsrc/mk/checksum and replace the "checksum" target command list with a script that does all the real work. * Make DIGEST_ALGORITHMS and PATCH_DIGEST_ALGORITHM into private variables by prepending them with an underscore. Also, rename _PATCH_DIGEST_ALGORITHM to _PATCH_DIGEST_ALGORITHMS and adjust the makepatchsum target to allow that variable to contain a list of algorithms, all of which are used when creating the patch checksums for ${DISTINFO_FILE}.
2006-07-13 16:02:34 +02:00
Introduce the capability to gather all the warnings and errors that are generated for a target and output them all at once at the conclusion of the target's invocation. The implementation is in bsd.pkg.error.mk, which defines a macro target "error-check" that will print out any non-empty warning and error files in ${WARNING_DIR} and ${ERROR_DIR} and exit appropriately if there were errors. Convert some targets that were just long sequences of ${ERROR_MSG} or ${WARNING_MSG} within a single shell statement to use the new delayed error output via error-check. Modify the compiler "fail" wrappers for C++ and Fortran to be less verbose during invocation. Instead collect the warnings and only print them at the end of the completed phase, e.g. after "configure" and/or "build" completes.
2006-06-09 15:59:06 +02:00
.include "${PKGSRCDIR}/mk/bsd.pkg.error.mk"
Move some variable definitions out of bsd.prefs.mk and back into bsd.pkg.mk. They didn't actually need to be defined in bsd.prefs.mk, just somewhere before the "main" bsd.<phase>.mk files were included. This moves some conditional (?=) definitions back into bsd.pkg.mk so they won't conflict with any conditional definitions in package Makefiles. This should fix the "checksum" problems in lang/php-gd as noted here: http://mail-index.netbsd.org/pkgsrc-users/2006/06/05/0012.html where EXTRACT_SUFX had the wrong value due to the order in while *.mk files were included.
2006-06-06 17:28:51 +02:00
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
.include "../../mk/bsd.hacks.mk"
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
# This has to come first to avoid showing all BUILD_DEFS added by this
# Makefile, which are usually not customizable.
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
.PHONY: build-defs-message
pre-depends-hook: build-defs-message
oops.. reversed a test
2004-08-05 01:29:50 +02:00
.if empty(PKGSRC_SHOW_BUILD_DEFS:M[yY][eE][sS])
Re-model the BUILD_DEFS display during build: if PKGSRC_SHOW_BUILD_DEFS is defined, then show the BUILD_DEFS to the user. If not, then just keep quiet. Whilst I'm here, re-indent the cpp-like .if/.else/.endif/.for/.endfor lines properly. Also, remove the ":u" modifier in the build-defs-message code - it's not strictly necessary (duplicate definitions will be displayed, but this isn't a major problem), and it removes the requirement to have a make(1) binary which supports ":u". This should fix PR 22402 from Alan Barrett, and also addresses some concerns raised by Robert Elz.
2003-08-08 10:43:37 +02:00
build-defs-message:
.elif !target(build-defs-message)
Modify the build-defs-message target so that it is only printed once, in the pre-fetch stage. Do this by creating a cookie file inside the WRKDIR. Also let the user override the target from mk.conf to disable these messages. This fixes PR pkg/22305 by Robert Elz.
2003-07-30 17:04:21 +02:00
build-defs-message: ${WRKDIR}
Re-model the BUILD_DEFS display during build: if PKGSRC_SHOW_BUILD_DEFS is defined, then show the BUILD_DEFS to the user. If not, then just keep quiet. Whilst I'm here, re-indent the cpp-like .if/.else/.endif/.for/.endfor lines properly. Also, remove the ":u" modifier in the build-defs-message code - it's not strictly necessary (duplicate definitions will be displayed, but this isn't a major problem), and it removes the requirement to have a make(1) binary which supports ":u". This should fix PR 22402 from Alan Barrett, and also addresses some concerns raised by Robert Elz.
2003-08-08 10:43:37 +02:00
. if defined(BUILD_DEFS) && !empty(BUILD_DEFS)
. if !exists(${WRKDIR}/.bdm_done)
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
@${ECHO} "=========================================================================="
@${ECHO} "The following variables will affect the build process of this package,"
@${ECHO} "${PKGNAME}. Their current value is shown below:"
@${ECHO} ""
Re-model the BUILD_DEFS display during build: if PKGSRC_SHOW_BUILD_DEFS is defined, then show the BUILD_DEFS to the user. If not, then just keep quiet. Whilst I'm here, re-indent the cpp-like .if/.else/.endif/.for/.endfor lines properly. Also, remove the ":u" modifier in the build-defs-message code - it's not strictly necessary (duplicate definitions will be displayed, but this isn't a major problem), and it removes the requirement to have a make(1) binary which supports ":u". This should fix PR 22402 from Alan Barrett, and also addresses some concerns raised by Robert Elz.
2003-08-08 10:43:37 +02:00
. for var in ${BUILD_DEFS:O}
. if !defined(${var})
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
@${ECHO} " * ${var} (not defined)"
Re-model the BUILD_DEFS display during build: if PKGSRC_SHOW_BUILD_DEFS is defined, then show the BUILD_DEFS to the user. If not, then just keep quiet. Whilst I'm here, re-indent the cpp-like .if/.else/.endif/.for/.endfor lines properly. Also, remove the ":u" modifier in the build-defs-message code - it's not strictly necessary (duplicate definitions will be displayed, but this isn't a major problem), and it removes the requirement to have a make(1) binary which supports ":u". This should fix PR 22402 from Alan Barrett, and also addresses some concerns raised by Robert Elz.
2003-08-08 10:43:37 +02:00
. elif defined(${var}) && empty(${var})
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
@${ECHO} " * ${var} (defined)"
Re-model the BUILD_DEFS display during build: if PKGSRC_SHOW_BUILD_DEFS is defined, then show the BUILD_DEFS to the user. If not, then just keep quiet. Whilst I'm here, re-indent the cpp-like .if/.else/.endif/.for/.endfor lines properly. Also, remove the ":u" modifier in the build-defs-message code - it's not strictly necessary (duplicate definitions will be displayed, but this isn't a major problem), and it removes the requirement to have a make(1) binary which supports ":u". This should fix PR 22402 from Alan Barrett, and also addresses some concerns raised by Robert Elz.
2003-08-08 10:43:37 +02:00
. else
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
@${ECHO} " * ${var} = ${${var}}"
Re-model the BUILD_DEFS display during build: if PKGSRC_SHOW_BUILD_DEFS is defined, then show the BUILD_DEFS to the user. If not, then just keep quiet. Whilst I'm here, re-indent the cpp-like .if/.else/.endif/.for/.endfor lines properly. Also, remove the ":u" modifier in the build-defs-message code - it's not strictly necessary (duplicate definitions will be displayed, but this isn't a major problem), and it removes the requirement to have a make(1) binary which supports ":u". This should fix PR 22402 from Alan Barrett, and also addresses some concerns raised by Robert Elz.
2003-08-08 10:43:37 +02:00
. endif
. endfor
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
@${ECHO} ""
wrap a long line in BUILD_DEFS output, tweak the message slightly.
2004-03-27 09:06:24 +01:00
@${ECHO} "You may want to abort the process now with CTRL-C and change their value"
@${ECHO} "before continuing. Be sure to run \`${MAKE} clean' after"
@${ECHO} "the changes."
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
@${ECHO} "=========================================================================="
Modify the build-defs-message target so that it is only printed once, in the pre-fetch stage. Do this by creating a cookie file inside the WRKDIR. Also let the user override the target from mk.conf to disable these messages. This fixes PR pkg/22305 by Robert Elz.
2003-07-30 17:04:21 +02:00
@${TOUCH} ${WRKDIR}/.bdm_done
Re-model the BUILD_DEFS display during build: if PKGSRC_SHOW_BUILD_DEFS is defined, then show the BUILD_DEFS to the user. If not, then just keep quiet. Whilst I'm here, re-indent the cpp-like .if/.else/.endif/.for/.endfor lines properly. Also, remove the ":u" modifier in the build-defs-message code - it's not strictly necessary (duplicate definitions will be displayed, but this isn't a major problem), and it removes the requirement to have a make(1) binary which supports ":u". This should fix PR 22402 from Alan Barrett, and also addresses some concerns raised by Robert Elz.
2003-08-08 10:43:37 +02:00
. endif
. endif
Add the build-defs-message target, which shows a list of all variables that can be customized for the package beeing built. This list is extracted from the contents of BUILD_DEFS, and the message is not shown if it's empty. Each variable is printed together with its actual value. The new target is called in the pre-fetch stage, so it's shown early to the user.
2003-07-28 20:15:56 +02:00
.endif
Merge down some more visual cleanup from tv-derecurse to reduce divergence. Part of this, introduce bsd.pkg.use.mk, where the Special Logic invoked by various pkgsrc-wide USE_* variables will be migrated/consolidated.
2005-02-11 16:55:13 +01:00
############################################################################
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
# Transform package Makefile variables and set defaults
Merge down some more visual cleanup from tv-derecurse to reduce divergence. Part of this, introduce bsd.pkg.use.mk, where the Special Logic invoked by various pkgsrc-wide USE_* variables will be migrated/consolidated.
2005-02-11 16:55:13 +01:00
############################################################################
Fail-safe check for circular dependencies.
2003-10-02 16:41:42 +02:00
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
MKCRYPTO?= YES # build crypto packages by default
##### Variant spellings
.if defined(LICENCE) && !defined(LICENSE)
LICENSE= ${LICENCE}
.endif
.if defined(ACCEPTABLE_LICENCES) && !defined(ACCEPTABLE_LICENSES)
ACCEPTABLE_LICENSES= ${ACCEPTABLE_LICENCES}
.endif
##### PKGBASE, PKGNAME[_NOREV], PKGVERSION
Implement some parts of proposals posted to tech-pkg: - Define OS_VERSION in bsd.prefs.mk (...if not already defined). Previously was only set in a conditional block in bsd.pkg.mk. - Define new values, MACHINE_PLATFORM and MACHINE_GNU_PLATFORM, which default to ${OPSYS}-${OS_VERSION}-${MACHINE_ARCH} and ${LOWER_OPSYS}-${LOWER_VENDOR}-${LOWER_ARCH} respectively. (Probably should nuke LOWER_ARCH and rename LOWER_VENDOR to something like MACHINE_GNU_VENDOR.) - Use ${MACHINE_GNU_PLATFORM} as the argument to `--host' in GNU_CONFIGURE packages. - Allow for ONLY_FOR_PLATFORM and NOT_FOR_PLATFORM, lists of patterns in csh(1) glob style which are matched against MACHINE_PLATFORM above and take the place of {ONLY,NOT}_FOR_{ARCHS,OPSYS}. (For now, until all pkgs are converted, provide backwards compatibility.) *Both* may be defined, in which case NOT_FOR_PLATFORM takes precedence. - Also do some significant aesthetic cleanup, based on the idea `define platform-specific overrides first, then define a generic case with the ?= operator'. Lots more of this to do yet.
1999-05-24 20:42:00 +02:00
Oops; use ?= for PKGBASE and PKGVERSION, so pkgs can derive their PKGNAMEs from them.
2000-06-03 21:03:20 +02:00
PKGBASE?= ${PKGNAME:C/-[^-]*$//}
PKGVERSION?= ${PKGNAME:C/^.*-//}
Move definition of PKGNAME and PKGNAME_NOREV higher in the file since their expanded values are used somewhere in the middle.
2004-09-15 17:26:10 +02:00
.if defined(PKGREVISION) && !empty(PKGREVISION) && (${PKGREVISION} != "0")
. if defined(PKGNAME)
PKGNAME_NOREV:= ${PKGNAME}
PKGNAME:= ${PKGNAME}nb${PKGREVISION}
. else
PKGNAME?= ${DISTNAME}nb${PKGREVISION}
PKGNAME_NOREV= ${DISTNAME}
. endif
.else
PKGNAME?= ${DISTNAME}
PKGNAME_NOREV= ${PKGNAME}
.endif
Add PKGPATH, PKGBASE, PKGVERSION and PKGWILDCARD make(1) variables, so that the substitution hacks are all done in one place. Protect a few things with double quotes just to be safe. Fix `readme' target that was left broken in last commit.
2000-06-03 20:51:34 +02:00
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
##### Others
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
Merge down some more visual cleanup from tv-derecurse to reduce divergence. Part of this, introduce bsd.pkg.use.mk, where the Special Logic invoked by various pkgsrc-wide USE_* variables will be migrated/consolidated.
2005-02-11 16:55:13 +01:00
BUILD_DEPENDS?= # empty
COMMENT?= (no description)
DEPENDS?= # empty
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
DESCR_SRC?= ${PKGDIR}/DESCR
Deprecate IS_INTERACTIVE, and introduce a finer-grained INTERACTIVE_STAGE 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).
2002-07-02 13:26:05 +02:00
INTERACTIVE_STAGE?= none
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER?= pkgsrc-users@NetBSD.org
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
PKGWILDCARD?= ${PKGBASE}-[0-9]*
SVR4_PKGNAME?= ${PKGNAME}
WRKSRC?= ${WRKDIR}/${DISTNAME}
Fix a gleaming illustration of why using YES/NO variables everywhere possible, just for the sake of doing so, is not a good thing to do: The platform files define _STRIPFLAG_* to determine whether to strip things. But since this is included in bsd.prefs.mk, ".if ..." checks cannot take things set in the Makefile into account. So convert INSTALL_UNSTRIPPED=YES to a defined/undefined variable check in bsd.pkg.mk, and use the :D:U idiom in the _STRIPFLAG_* variables. This should fix PR pkg/28772 and PR pkg/29031.
2005-03-18 19:16:34 +01:00
.if (defined(INSTALL_UNSTRIPPED) && !empty(INSTALL_UNSTRIPPED:M[yY][eE][sS])) || defined(DEBUG_FLAGS)
_INSTALL_UNSTRIPPED= # set (flag used by platform/*.mk)
.endif
Merge down some more visual cleanup from tv-derecurse to reduce divergence. Part of this, introduce bsd.pkg.use.mk, where the Special Logic invoked by various pkgsrc-wide USE_* variables will be migrated/consolidated.
2005-02-11 16:55:13 +01:00
##### Non-overridable constants
# Latest versions of tools required for correct pkgsrc operation.
Use new automatic flag; depend on appropriate pkg_install version.
2005-11-05 14:31:43 +01:00
PKGTOOLS_REQD= ${_OPSYS_PKGTOOLS_REQD:U20051103}
Merge down some more visual cleanup from tv-derecurse to reduce divergence. Part of this, introduce bsd.pkg.use.mk, where the Special Logic invoked by various pkgsrc-wide USE_* variables will be migrated/consolidated.
2005-02-11 16:55:13 +01:00
##### Transform USE_* into dependencies
.include "../../mk/bsd.pkg.use.mk"
Consolidate PLIST_SRC default generation and the plethora of failsafe error checks into labelled blocks toward the top of the file. While here, remove the historic (now completely empty; it was replaced by PKG_FAIL_REASON some time ago) uptodate-pkgtools target and the references to it.
2005-02-11 17:57:45 +01:00
############################################################################
# Sanity checks
############################################################################
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
# Fail-safe in the case of circular dependencies
.if defined(_PKGSRC_DEPS) && defined(PKGNAME) && !empty(_PKGSRC_DEPS:M${PKGNAME})
Whitespace formatting nits.
2005-02-11 18:00:07 +01:00
PKG_FAIL_REASON+= "Circular dependency detected"
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
.endif
Consolidate PLIST_SRC default generation and the plethora of failsafe error checks into labelled blocks toward the top of the file. While here, remove the historic (now completely empty; it was replaced by PKG_FAIL_REASON some time ago) uptodate-pkgtools target and the references to it.
2005-02-11 17:57:45 +01:00
# PKG_INSTALLATION_TYPE can only be one of two values: "pkgviews" or
# "overwrite".
.if (${PKG_INSTALLATION_TYPE} != "pkgviews") && \
(${PKG_INSTALLATION_TYPE} != "overwrite")
PKG_FAIL_REASON+= "PKG_INSTALLATION_TYPE must be \`\`pkgviews'' or \`\`overwrite''."
.endif
.if empty(PKG_INSTALLATION_TYPES:M${PKG_INSTALLATION_TYPE})
PKG_FAIL_REASON+= "This package doesn't support PKG_INSTALLATION_TYPE=${PKG_INSTALLATION_TYPE}."
.endif
# Check that we are using up-to-date pkg_* tools with this file.
.if !defined(NO_PKGTOOLS_REQD_CHECK)
. if ${PKGTOOLS_VERSION} < ${PKGTOOLS_REQD}
Output PKG_{FAIL,SKIP}_REASON messages to standard error instead of standard output. These are error or warning messages, so they shouldn't be "seen" by anything expecting the output of a "make" command to make sense. This addresses PR pkg/32239 by following the suggestions by Roland Illig.
2006-06-15 04:39:19 +02:00
PKG_FAIL_REASON+='The package tools installed on this system are out of date.'
PKG_FAIL_REASON+='The installed package tools are dated ${PKGTOOLS_VERSION:C|(....)(..)(..)|\1/\2/\3|} and you must'
PKG_FAIL_REASON+='update them to at least ${PKGTOOLS_REQD:C|(....)(..)(..)|\1/\2/\3|} using the following command:'
Consolidate PLIST_SRC default generation and the plethora of failsafe error checks into labelled blocks toward the top of the file. While here, remove the historic (now completely empty; it was replaced by PKG_FAIL_REASON some time ago) uptodate-pkgtools target and the references to it.
2005-02-11 17:57:45 +01:00
PKG_FAIL_REASON+=''
Output PKG_{FAIL,SKIP}_REASON messages to standard error instead of standard output. These are error or warning messages, so they shouldn't be "seen" by anything expecting the output of a "make" command to make sense. This addresses PR pkg/32239 by following the suggestions by Roland Illig.
2006-06-15 04:39:19 +02:00
PKG_FAIL_REASON+=' (cd ${PKGSRCDIR}/pkgtools/pkg_install && ${MAKE} clean && ${MAKE} update)'
Consolidate PLIST_SRC default generation and the plethora of failsafe error checks into labelled blocks toward the top of the file. While here, remove the historic (now completely empty; it was replaced by PKG_FAIL_REASON some time ago) uptodate-pkgtools target and the references to it.
2005-02-11 17:57:45 +01:00
. endif
.endif # !NO_PKGTOOLS_REQD_CHECK
.if defined(ALL_TARGET)
PKG_FAIL_REASON+='ALL_TARGET is deprecated and must be replaced with BUILD_TARGET.'
.endif
.if defined(NO_WRKSUBDIR)
PKG_FAIL_REASON+='NO_WRKSUBDIR has been deprecated - please replace it with an explicit'
PKG_FAIL_REASON+='assignment of WRKSRC= $${WRKDIR}'
.endif # NO_WRKSUBDIR
# We need to make sure the buildlink-x11 package is not installed since it
# breaks builds that use imake.
.if defined(USE_IMAKE)
. if exists(${LOCALBASE}/lib/X11/config/buildlinkX11.def) || \
exists(${X11BASE}/lib/X11/config/buildlinkX11.def)
PKG_FAIL_REASON+= "${PKGNAME} uses imake, but the buildlink-x11 package was found." \
" Please deinstall it (pkg_delete buildlink-x11)."
. endif
.endif # USE_IMAKE
.if !defined(CATEGORIES) || !defined(DISTNAME)
PKG_FAIL_REASON+='CATEGORIES and DISTNAME are mandatory.'
.endif
.if defined(LIB_DEPENDS)
PKG_FAIL_REASON+='LIB_DEPENDS is deprecated and must be replaced with DEPENDS.'
.endif
.if defined(PKG_PATH)
PKG_FAIL_REASON+='Please unset PKG_PATH before doing pkgsrc work!'
.endif
.if defined(MASTER_SITE_SUBDIR)
PKG_FAIL_REASON+='MASTER_SITE_SUBDIR is deprecated and must be replaced with MASTER_SITES.'
.endif
.if defined(PATCH_SITE_SUBDIR)
PKG_FAIL_REASON+='PATCH_SITE_SUBDIR is deprecated and must be replaced with PATCH_SITES.'
.endif
.if defined(ONLY_FOR_ARCHS) || defined(NOT_FOR_ARCHS) \
|| defined(ONLY_FOR_OPSYS) || defined(NOT_FOR_OPSYS)
PKG_FAIL_REASON+='ONLY/NOT_FOR_ARCHS/OPSYS are deprecated and must be replaced with ONLY/NOT_FOR_PLATFORM.'
.endif
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
# Allow variables to be set on a per-OS basis
OPSYSVARS+= CFLAGS CXXFLAGS CPPFLAGS LDFLAGS LIBS
.for _var_ in ${OPSYSVARS:O}
. if defined(${_var_}.${OPSYS})
${_var_}+= ${${_var_}.${OPSYS}}
. elif defined(${_var_}.*)
${_var_}+= ${${_var_}.*}
. endif
.endfor
Visual cleanup from tv-derecurse: Consolidate many MAKE_ENVs and SCRIPTS_ENVs into a common block. (CONFIGURE_ENVs to be done later.) Introduce new variable ALL_ENV which is automatically included into all of MAKE_ENV, SCRIPTS_ENV, and CONFIGURE_ENV; this allows much cleaner addition of the common CC/CXX/CFLAGS/etc. variables needed by all of these.
2005-02-11 17:36:49 +01:00
CPPFLAGS+= ${CPP_PRECOMP_FLAGS}
Removed trailing white-space.
2005-11-14 05:41:17 +01:00
Visual cleanup from tv-derecurse: Consolidate many MAKE_ENVs and SCRIPTS_ENVs into a common block. (CONFIGURE_ENVs to be done later.) Introduce new variable ALL_ENV which is automatically included into all of MAKE_ENV, SCRIPTS_ENV, and CONFIGURE_ENV; this allows much cleaner addition of the common CC/CXX/CFLAGS/etc. variables needed by all of these.
2005-02-11 17:36:49 +01:00
ALL_ENV+= CC=${CC:Q}
In make variables, quotes protect embedded whitespace in words, so we can replace :C/^ *//:C/ *$// with :M* to get the same effect -- removing leading and trailing whitespace and extra spaces between words.
2005-05-10 03:34:04 +02:00
ALL_ENV+= CFLAGS=${CFLAGS:M*:Q}
ALL_ENV+= CPPFLAGS=${CPPFLAGS:M*:Q}
ALL_ENV+= CXX=${CXX:M*:Q}
ALL_ENV+= CXXFLAGS=${CXXFLAGS:M*:Q}
Visual cleanup from tv-derecurse: Consolidate many MAKE_ENVs and SCRIPTS_ENVs into a common block. (CONFIGURE_ENVs to be done later.) Introduce new variable ALL_ENV which is automatically included into all of MAKE_ENV, SCRIPTS_ENV, and CONFIGURE_ENV; this allows much cleaner addition of the common CC/CXX/CFLAGS/etc. variables needed by all of these.
2005-02-11 17:36:49 +01:00
ALL_ENV+= COMPILER_RPATH_FLAG=${COMPILER_RPATH_FLAG:Q}
make sure we correctly set F77. Addresses PR29666
2005-03-16 03:09:54 +01:00
ALL_ENV+= F77=${FC:Q}
Visual cleanup from tv-derecurse: Consolidate many MAKE_ENVs and SCRIPTS_ENVs into a common block. (CONFIGURE_ENVs to be done later.) Introduce new variable ALL_ENV which is automatically included into all of MAKE_ENV, SCRIPTS_ENV, and CONFIGURE_ENV; this allows much cleaner addition of the common CC/CXX/CFLAGS/etc. variables needed by all of these.
2005-02-11 17:36:49 +01:00
ALL_ENV+= FC=${FC:Q}
In make variables, quotes protect embedded whitespace in words, so we can replace :C/^ *//:C/ *$// with :M* to get the same effect -- removing leading and trailing whitespace and extra spaces between words.
2005-05-10 03:34:04 +02:00
ALL_ENV+= FFLAGS=${FFLAGS:M*:Q}
Reset the current locale to a sane value (that is, 'C') during the build of packages. Several utilities behave differently or even incorrectly if a locale different than 'C' is set. One of these is perl, which spits a big warning and then breaks some packages. An example is irssi, as described in PR pkg/29613 by Hanno Wagner.
2005-03-20 19:18:09 +01:00
ALL_ENV+= LANG=C
ALL_ENV+= LC_COLLATE=C
ALL_ENV+= LC_CTYPE=C
ALL_ENV+= LC_MESSAGES=C
ALL_ENV+= LC_MONETARY=C
ALL_ENV+= LC_NUMERIC=C
ALL_ENV+= LC_TIME=C
In make variables, quotes protect embedded whitespace in words, so we can replace :C/^ *//:C/ *$// with :M* to get the same effect -- removing leading and trailing whitespace and extra spaces between words.
2005-05-10 03:34:04 +02:00
ALL_ENV+= LDFLAGS=${LDFLAGS:M*:Q}
Visual cleanup from tv-derecurse: Consolidate many MAKE_ENVs and SCRIPTS_ENVs into a common block. (CONFIGURE_ENVs to be done later.) Introduce new variable ALL_ENV which is automatically included into all of MAKE_ENV, SCRIPTS_ENV, and CONFIGURE_ENV; this allows much cleaner addition of the common CC/CXX/CFLAGS/etc. variables needed by all of these.
2005-02-11 17:36:49 +01:00
ALL_ENV+= LINKER_RPATH_FLAG=${LINKER_RPATH_FLAG:Q}
ALL_ENV+= PATH=${PATH:Q}:${LOCALBASE}/bin:${X11BASE}/bin
ALL_ENV+= PREFIX=${PREFIX}
Merge a little visual-only cleanup from the tv-derecurse branch: Collect many modifiable hard-to-find variables scattered throughout bsd.pkg.mk into a common section near the top of the file. (Not necessarily "complete", but helps to reduce HEAD-branch divergence.)
2005-01-24 20:57:42 +01:00
# Store the result in the +BUILD_INFO file so we can query for the build
# options using "pkg_info -Q PKG_OPTIONS <pkg>".
#
.if defined(PKG_SUPPORTED_OPTIONS) && defined(PKG_OPTIONS)
BUILD_DEFS+= PKG_OPTIONS
.endif
Deprecate IS_INTERACTIVE, and introduce a finer-grained INTERACTIVE_STAGE 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).
2002-07-02 13:26:05 +02:00
Merge pkgviews-mk branch into the HEAD by running: cd pkgsrc/mk cvs update -Pd -A cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
2003-09-02 08:59:37 +02:00
.if empty(DEPOT_SUBDIR)
PKG_FAIL_REASON+= "DEPOT_SUBDIR may not be empty."
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
.endif
- Integrate xpkgwedge with a switch, USE_LOCALBASE_FOR_X11, which leaves X11BASE alone and, when set, sets PREFIX to LOCALBASE and adds a build dependency on xpkgwedge - Nuke last vestiges of the ${ARCH} variable, and replace it with the binary compatibility identifier ${MACHINE_ARCH}. - Include bsd.prefs.mk early in bsd.pkg.mk. (Needed by xpkgwedge change.) - Look for Motif/lesstif in both X11BASE and LOCALBASE - Add rpath (-Wl,-R) options for MOTIFLIB - Nuke obsolete EXEC_DEPENDS cruft
1998-07-31 16:55:38 +02:00
If there is _ZERO_FILESIZE_P, then it's natural to have _NONZERO_FILESIZE_P to test for the opposite condition.
2006-06-07 20:37:06 +02:00
# ZERO_FILESIZE_P exits with a successful return code if the given file
# has zero length.
# NONZERO_FILESIZE_P exits with a successful return code if the given file
# has nonzero length.
Move _ZERO_FILESIZE_P ftom bsd.pkginstall.mk to bsd.pkg.mk so it can more clearly be used in other modules.
2006-06-07 19:44:29 +02:00
#
If there is _ZERO_FILESIZE_P, then it's natural to have _NONZERO_FILESIZE_P to test for the opposite condition.
2006-06-07 20:37:06 +02:00
_ZERO_FILESIZE_P= ${AWK} 'END { exit (NR > 0) ? 1 : 0; }'
_NONZERO_FILESIZE_P= ${AWK} 'END { exit (NR > 0) ? 0 : 1; }'
Move _ZERO_FILESIZE_P ftom bsd.pkginstall.mk to bsd.pkg.mk so it can more clearly be used in other modules.
2006-06-07 19:44:29 +02:00
Add a new variable "UNLIMIT_RESOURCES" which can be used to raise process limits for building a package.
2002-01-04 13:00:56 +01:00
# Automatically increase process limit where necessary for building.
Collapse two .for blocks to improve readability: _ULIMIT_CMD to use a ${...:@var@loop ...@} construct _ACCEPTABLE to use a !empty(var:Mfoo) conditional
2005-11-18 18:07:13 +01:00
_ULIMIT_CMD= ${UNLIMIT_RESOURCES:@_lim_@${ULIMIT_CMD_${_lim_}};@}
Add a new variable "UNLIMIT_RESOURCES" which can be used to raise process limits for building a package.
2002-01-04 13:00:56 +01:00
Introduce the capability to gather all the warnings and errors that are generated for a target and output them all at once at the conclusion of the target's invocation. The implementation is in bsd.pkg.error.mk, which defines a macro target "error-check" that will print out any non-empty warning and error files in ${WARNING_DIR} and ${ERROR_DIR} and exit appropriately if there were errors. Convert some targets that were just long sequences of ${ERROR_MSG} or ${WARNING_MSG} within a single shell statement to use the new delayed error output via error-check. Modify the compiler "fail" wrappers for C++ and Fortran to be less verbose during invocation. Instead collect the warnings and only print them at the end of the completed phase, e.g. after "configure" and/or "build" completes.
2006-06-09 15:59:06 +02:00
_INTERACTIVE_COOKIE= ${.CURDIR}/.interactive_stage
Added a leading underscore to the names of the *_COOKIE variables, as they are not part of the public interface.
2005-06-04 22:56:47 +02:00
_NULL_COOKIE= ${WRKDIR}/.null
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
# Miscellaneous overridable commands:
Add code to include the size of a package into both the installed version and binary packages. The size can be queried then via pkg_info: xfeyrer @ noon% pkg_info -s xv Information for xv-3.10apl1: Size of this package in bytes: 4670692 xfeyrer @ noon% pkg_info -S xv Information for xv-3.10apl1: Size in bytes including required pkgs: 14610165 While doing work on the size code, support for the @src directive was removed (formerly enabled with the pkg_create -s switch, but unused in our pkg system). The new pkg_info -s and -S switches were tested on installed, local (file) and remote (ftp) packages. In bsd.pkg.mk, take special care for pkg_* versions that do not have the pkg_create -s and -S switches and do not record size information there.
1999-11-29 20:48:15 +01:00
SHCOMMENT?= ${ECHO_MSG} >/dev/null '***'
Add support for message digests other than md5 into pkgsrc. This is done by using the pkgsrc/pkgtools/digest package, and adding dependencies in bsd.pkg.mk to make sure that that package is up to date. There is no discernable performance decrease in using sha1 checksums over md5 ones, and most people advocate the use of sha1 or rmd160 over md5. As part of this change, move the initial setting of LOCALBASE, X11BASE and CROSSBASE into bsd.prefs.mk from bsd.pkg.mk. Addresses PR 11809.
2001-03-06 15:50:45 +01:00
Introduce LIBABISUFFIX for platforms which require ABI-dependant library paths.
2004-11-12 21:25:41 +01:00
LIBABISUFFIX?=
Implement some parts of proposals posted to tech-pkg: - Define OS_VERSION in bsd.prefs.mk (...if not already defined). Previously was only set in a conditional block in bsd.pkg.mk. - Define new values, MACHINE_PLATFORM and MACHINE_GNU_PLATFORM, which default to ${OPSYS}-${OS_VERSION}-${MACHINE_ARCH} and ${LOWER_OPSYS}-${LOWER_VENDOR}-${LOWER_ARCH} respectively. (Probably should nuke LOWER_ARCH and rename LOWER_VENDOR to something like MACHINE_GNU_VENDOR.) - Use ${MACHINE_GNU_PLATFORM} as the argument to `--host' in GNU_CONFIGURE packages. - Allow for ONLY_FOR_PLATFORM and NOT_FOR_PLATFORM, lists of patterns in csh(1) glob style which are matched against MACHINE_PLATFORM above and take the place of {ONLY,NOT}_FOR_{ARCHS,OPSYS}. (For now, until all pkgs are converted, provide backwards compatibility.) *Both* may be defined, in which case NOT_FOR_PLATFORM takes precedence. - Also do some significant aesthetic cleanup, based on the idea `define platform-specific overrides first, then define a generic case with the ?= operator'. Lots more of this to do yet.
1999-05-24 20:42:00 +02:00
TOUCH_FLAGS?= -f
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
Add Solaris support to pkgsrc, using Christos Zoulas' NetBSD emulation package. Tested for some packages on Solaris 2.6 on Sparc.
1999-03-08 18:26:54 +01:00
# Debugging levels for this file, dependent on PKG_DEBUG_LEVEL definition
# 0 == normal, default, quiet operation
# 1 == all shell commands echoed before invocation
# 2 == shell "set -x" operation
PKG_DEBUG_LEVEL?= 0
_PKG_SILENT= @
When PKG_DEBUG_LEVEL=2, set_PKG_DEBUG_SCRIPT is set to "${SH} -x". Use _PKG_DEBUG_SCRIPT when running the INSTALL/DEINSTALL scripts so that they may be easier to debug.
2002-09-26 23:04:11 +02:00
_PKG_DEBUG= # empty
_PKG_DEBUG_SCRIPT= # empty
Add Solaris support to pkgsrc, using Christos Zoulas' NetBSD emulation package. Tested for some packages on Solaris 2.6 on Sparc.
1999-03-08 18:26:54 +01:00
.if ${PKG_DEBUG_LEVEL} > 0
When PKG_DEBUG_LEVEL=2, set_PKG_DEBUG_SCRIPT is set to "${SH} -x". Use _PKG_DEBUG_SCRIPT when running the INSTALL/DEINSTALL scripts so that they may be easier to debug.
2002-09-26 23:04:11 +02:00
_PKG_SILENT= # empty
Add Solaris support to pkgsrc, using Christos Zoulas' NetBSD emulation package. Tested for some packages on Solaris 2.6 on Sparc.
1999-03-08 18:26:54 +01:00
.endif
.if ${PKG_DEBUG_LEVEL} > 1
_PKG_DEBUG= set -x;
When PKG_DEBUG_LEVEL=2, set_PKG_DEBUG_SCRIPT is set to "${SH} -x". Use _PKG_DEBUG_SCRIPT when running the INSTALL/DEINSTALL scripts so that they may be easier to debug.
2002-09-26 23:04:11 +02:00
_PKG_DEBUG_SCRIPT= ${SH} -x
- Add OpenBSD and FreeBSD Ids in the header - Changes from FreeBSD's V1.164: * Warn if mtree-file not found * On 'make reinstall' gets DEPENDS_TARGET set to 'reinstall' instead of 'install' - Changes from OpenBSD's V1.14: * Documentation and implementation for ONLY_FOR_ARCHS * Documentation and implementation for WRKOBJDIR * Documentation on HAVE_MOTIF and MOTIF_STATIC: set in /etc/mk.conf, not /etc/make.conf * Set NOMANCOMPRESS=no to still compress man-pages (should probably be set to 'yes') * DEF_UMASK=022 * add ${MACHINE} suffix to WRKDIR if OBJMACHINE is set * .include <bsd.own.mk>
1997-09-28 02:44:15 +02:00
.endif
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
# A few aliases for *-install targets
Override the INSTALL setting in sys.mk that messes up the rest of the logic in the tools framework.
2005-07-17 06:17:09 +02:00
INSTALL= ${TOOLS_INSTALL} # XXX override sys.mk
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_PROGRAM?= \
Replace STRIPFLAG with _STRIPFLAG_INSTALL to fix pkg/15467.
2002-05-29 16:52:14 +02:00
${INSTALL} ${COPY} ${_STRIPFLAG_INSTALL} -o ${BINOWN} -g ${BINGRP} -m ${BINMODE}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_GAME?= \
${INSTALL} ${COPY} ${_STRIPFLAG_INSTALL} -o ${GAMEOWN} -g ${GAMEGRP} -m ${GAMEMODE}
INSTALL_SCRIPT?= \
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${BINMODE}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_LIB?= \
Add a new install macro INSTALL_LIB for use when installing libraries (mainly intended for shlib use, but for homeful use on all libraries so that currently static libs can be "provisioned" for future shlib use).
2004-04-28 00:35:47 +02:00
${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${BINMODE}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_DATA?= \
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
${INSTALL} ${COPY} -o ${SHAREOWN} -g ${SHAREGRP} -m ${SHAREMODE}
Introduce GAMEDATAMODE and INSTALL_GAME_DATA, which will take care of files installed for SETGIDGAME packages. This will help address PR pkg/25313 and PR pkg/26236.
2004-08-04 04:56:01 +02:00
INSTALL_GAME_DATA?= \
${INSTALL} ${COPY} -o ${GAMEOWN} -g ${GAMEGRP} -m ${GAMEDATAMODE}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_MAN?= \
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
${INSTALL} ${COPY} -o ${MANOWN} -g ${MANGRP} -m ${MANMODE}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_PROGRAM_DIR?= \
Create directories with mode 0755, since that is what the mtree files expect. Noted by Toru TAKAMIZU in PR 22007, patch from seb@netbsd.
2003-07-12 12:21:33 +02:00
${INSTALL} -d -o ${BINOWN} -g ${BINGRP} -m ${PKGDIRMODE}
Add INSTALL_GAME_DIR to complement INSTALL_GAME_DATA. The directories are group-writeable by the games user on those platforms, where GAMEMODE includes setgid. It defaults to PKGDIRMODE otherwise.
2006-04-12 23:01:15 +02:00
INSTALL_GAME_DIR?= \
${INSTALL} -d -o ${GAMEOWN} -g ${GAMEGRP} -m ${GAMEDIRMODE}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_SCRIPT_DIR?= \
Add INSTALL_*_DIR macros.
1998-03-07 22:19:00 +01:00
${INSTALL_PROGRAM_DIR}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_LIB_DIR?= \
Add a new install macro INSTALL_LIB for use when installing libraries (mainly intended for shlib use, but for homeful use on all libraries so that currently static libs can be "provisioned" for future shlib use).
2004-04-28 00:35:47 +02:00
${INSTALL_PROGRAM_DIR}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_DATA_DIR?= \
Create directories with mode 0755, since that is what the mtree files expect. Noted by Toru TAKAMIZU in PR 22007, patch from seb@netbsd.
2003-07-12 12:21:33 +02:00
${INSTALL} -d -o ${SHAREOWN} -g ${SHAREGRP} -m ${PKGDIRMODE}
Introduce new variables: 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.
2004-05-12 03:03:58 +02:00
INSTALL_MAN_DIR?= \
Create directories with mode 0755, since that is what the mtree files expect. Noted by Toru TAKAMIZU in PR 22007, patch from seb@netbsd.
2003-07-12 12:21:33 +02:00
${INSTALL} -d -o ${MANOWN} -g ${MANGRP} -m ${PKGDIRMODE}
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
Fixed some quoting issues.
2005-05-22 17:31:03 +02:00
INSTALL_MACROS= BSD_INSTALL_PROGRAM=${INSTALL_PROGRAM:Q} \
BSD_INSTALL_SCRIPT=${INSTALL_SCRIPT:Q} \
BSD_INSTALL_LIB=${INSTALL_LIB:Q} \
BSD_INSTALL_DATA=${INSTALL_DATA:Q} \
BSD_INSTALL_MAN=${INSTALL_MAN:Q} \
BSD_INSTALL=${INSTALL:Q} \
BSD_INSTALL_PROGRAM_DIR=${INSTALL_PROGRAM_DIR:Q} \
BSD_INSTALL_SCRIPT_DIR=${INSTALL_SCRIPT_DIR:Q} \
BSD_INSTALL_LIB_DIR=${INSTALL_LIB_DIR:Q} \
BSD_INSTALL_DATA_DIR=${INSTALL_DATA_DIR:Q} \
BSD_INSTALL_MAN_DIR=${INSTALL_MAN_DIR:Q} \
BSD_INSTALL_GAME=${INSTALL_GAME:Q} \
Add INSTALL_GAME_DIR to complement INSTALL_GAME_DATA. The directories are group-writeable by the games user on those platforms, where GAMEMODE includes setgid. It defaults to PKGDIRMODE otherwise.
2006-04-12 23:01:15 +02:00
BSD_INSTALL_GAME_DATA=${INSTALL_GAME_DATA:Q} \
BSD_INSTALL_GAME_DIR=${INSTALL_GAME_DIR:Q}
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
MAKE_ENV+= ${INSTALL_MACROS}
SCRIPTS_ENV+= ${INSTALL_MACROS}
Always run the pkginstall framework targets to generate the INSTALL/DEINSTALL and rc.d scripts, regardless of whether NO_BUILD is defined or not. We do this by renaming the main "build" target to "_build", and creating a new "build" target that has "_build" and "pkginstall" as dependencies. This allows the "build" and "install" targets to be consecutive, so no changes in behavior are visible to the user. Because the pkginstall targets are no longer run within the protection of the locks during the build phase, we need to manage locking within a new "pkginstall" target.
2006-03-15 17:20:11 +01:00
# If pkgsrc is supposed to ensure that tests are run before installation
# of the package, then the build targets should be "build test", otherwise
# just "build" suffices.
#
.if !empty(PKGSRC_RUN_TEST:M[yY][eE][sS])
_PKGSRC_BUILD_TARGETS= build test
.else
_PKGSRC_BUILD_TARGETS= build
.endif
Refactor configure, build, test and wrapper phases out of bsd.pkg.mk and into their own directories. Also do some cleanups with build/_build and pkginstall -- we get rid of _build and simply run pkginstall as part of the "build" target. Introduce a new mechanism to handle varying directory depths under ${WRKSRC} in which we find files to override, e.g. configure, config.*, libtool, etc. OVERRIDE_DIRDEPTH is a package-settable variable that specifies how far under ${WRKSRC} the various targets should look, and it defaults to "2". We preserve the meaning of the various *_OVERRIDE variables, so if they are defined, then their values supersede the OVERRIDE_DIRDEPTH mechanism. devel/tla will need to specially set OVERRIDE_DIRDEPTH to 3 (see log for revision 1.1857 for bsd.pkg.mk -- to be done in a separate commit.
2006-07-05 08:09:15 +02:00
# OVERRIDE_DIRDEPTH represents the common directory depth under
# ${WRKSRC} up to which we find the files that need to be
# overridden. By default, we search two levels down, i.e.,
# */*/file.
#
OVERRIDE_DIRDEPTH?= 2
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
# The user can override the NO_PACKAGE by specifying this from
# the make command line
.if defined(FORCE_PACKAGE)
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. undef NO_PACKAGE
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
.endif
Add alternatives.mk, a file used to manipulate the alternatives system. A package can optionally provide an ALTERNATIVES file which contains pairs of wrapper/alternative, one per line. The file is then used by the install and deinstall scripts to register the alternatives and to create the appropriate wrappers. Make bsd.pkg.mk include this new file. This happens unconditionally to keep all the alternatives logic in an independent file. Otherwise, some of the stuff could have to be moved to bsd.pkg.mk, breaking consistency.
2005-01-25 14:13:35 +01:00
# Handle alternatives
#
.include "../../mk/alternatives.mk"
Modify the pkginstall framework so that it manages all aspects of INSTALL/DEINSTALL script creation within pkgsrc. If an INSTALL or DEINSTALL script is found in the package directory, it is automatically used as a template for the pkginstall-generated scripts. If instead, they should be used simply as the full scripts, then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC explicitly, e.g.: INSTALL_SRC= ${PKGDIR}/INSTALL DEINSTALL_SRC= # emtpy As part of the restructuring of the pkginstall framework internals, we now *always* generate temporary INSTALL or DEINSTALL scripts. By comparing these temporary scripts with minimal INSTALL/DEINSTALL scripts formed from only the base templates, we determine whether or not the INSTALL/DEINSTALL scripts are actually needed by the package (see the generate-install-scripts target in bsd.pkginstall.mk). In addition, more variables in the framework have been made private. The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are more sensible names given the very few exported variables in this framework. The only public variables relating to the templates are: INSTALL_SRC INSTALL_TEMPLATE DEINSTALL_SRC DEINSTALL_TEMPLATE HEADER_TEMPLATE The packages in pkgsrc have been modified to reflect the changes in the pkginstall framework.
2006-03-14 02:14:26 +01:00
# INSTALL/DEINSTALL script framework
Move mk/install to mk/pkginstall to better reflect the contents (the pkginstall framework).
2006-05-22 01:50:15 +02:00
.include "../../mk/pkginstall/bsd.pkginstall.mk"
Move the inclusion of bsd.pkg.install.mk higher so that binary packages are generated correctly (with INSTALL and DEINSTALL scripts). Fix suggested by Stoned Elipot <seb@netbsd.org>.
2003-01-29 20:34:14 +01:00
Previous commit to bsd.pkg.mk caught some "SMART_MESSAGES" work - document them now, in mk.conf.example, and add a small comment explaining what they do. When SMART_MESSAGES is defined, when compiling packages, the make(1) target is displayed, and also the current stack of packages being built.
2000-03-13 15:24:27 +01:00
# Define SMART_MESSAGES in /etc/mk.conf for messages giving the tree
Typo in comment for SMART_MESSAGES.
2001-01-31 00:18:36 +01:00
# of dependencies for building, and the current target.
Use :D and :U constructs in a few more places to collapse some .if defined blocks to a more parallelism-readable state.
2005-11-18 15:40:21 +01:00
_PKGSRC_IN?= ===${SMART_MESSAGES:D> ${.TARGET} [${PKGNAME}${_PKGSRC_DEPS}] ===}
Fix PACKAGE_DEPENDS_QUICK when installing on Solaris - escape the argument from the shell, so that we can install packages on Solaris again, and use canonical ${GREP} and ${AWK} programs.
2000-03-13 15:19:15 +01:00
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
# Used to print all the '===>' style prompts - override this to turn them off.
ECHO_MSG?= ${ECHO}
Added the variable PHASE_MSG, STEP_MSG, WARNING_MSG and ERROR_MSG to facilitate the generation of consistent-looking progress messages.
2006-03-12 15:55:18 +01:00
PHASE_MSG?= ${ECHO_MSG} ${_PKGSRC_IN:Q}\>
STEP_MSG?= ${ECHO_MSG} "=>"
WARNING_MSG?= ${ECHO_MSG} 1>&2 "WARNING:"
ERROR_MSG?= ${ECHO_MSG} 1>&2 "ERROR:"
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
Add WARNING_CAT and ERROR_CAT which are filters for outputting file contents to standard error. They prefix the output with "WARNING: " and "ERROR: " respectively.
2006-06-07 19:00:03 +02:00
WARNING_CAT?= ${SED} -e "s|^|WARNING: |" 1>&2
ERROR_CAT?= ${SED} -e "s|^|ERROR: |" 1>&2
Introduce TRUE?=/usr/bin/true, and use it.
1998-02-02 09:10:41 +01:00
# How to do nothing. Override if you, for some strange reason, would rather
# do something.
DO_NADA?= ${TRUE}
Move the PKG_SYSCONFDIR logic below the definition of PKGNAME. PKGNAME is use to set PKGBASE, which is used in the name of the package-specific config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if PKGNAME wasn't explicitly set in the package, then the override would not work.
2001-11-28 20:55:31 +01:00
#
Refer doc/pkgsrc.txt instead of Packages.txt.
2005-05-08 00:16:38 +02:00
# Config file related settings - see doc/pkgsrc.txt
Create a new knob: PKG_SYSCONFVAR PKG_SYSCONFVAR is the special suffix used to distinguish any overriding values for a particular package (see next item). It defaults to ${PKGNAME}, but for a collection of related packages that should all have the same PKG_SYSCONFDIR value, it can be set in each of the package Makefiles to a common value. PKG_SYSCONFDIR.${PKG_SYSCONFVAR} overrides the value of ${PKG_SYSCONFDIR} for packages with the same value for PKG_SYSCONFVAR. Package maintainers may want to set PKG_SYSCONFVAR to a common value for related packages, e.g. all of the amanda packages set PKG_SYSCONFVAR=amanda so that the PKG_SYSCONFDIR for all of them may be tweaked by just setting PKG_SYSCONFDIR.amanda in /etc/mk.conf.
2002-02-07 21:34:21 +01:00
#
PKG_SYSCONFVAR?= ${PKGBASE}
Move the PKG_SYSCONFDIR logic below the definition of PKGNAME. PKGNAME is use to set PKGBASE, which is used in the name of the package-specific config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if PKGNAME wasn't explicitly set in the package, then the override would not work.
2001-11-28 20:55:31 +01:00
PKG_SYSCONFSUBDIR?= # empty
Set DFLT_PKG_SYSCONDIR to the location that PKG_SYSCONFDIR would have been set to if it hadn't been overridden by PKG_SYSCONFDIR.<pkg>. This can be used in /etc/mk.conf to re-override certain PKG_SYSCONFDIR.<pkg> in /etc/mk.conf from various package Makefiles, e.g. PKG_SYSCONFDIR.openssl= ${DFLT_PKG_SYSCONFDIR} PKG_SYSCONFDIR.tcp_wrappers= ${DFLT_PKG_SYSCONFDIR}
2004-03-29 08:49:04 +02:00
.if ${PKG_INSTALLATION_TYPE} == "overwrite"
Merge pkgviews-mk branch into the HEAD by running: cd pkgsrc/mk cvs update -Pd -A cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
2003-09-02 08:59:37 +02:00
PKG_SYSCONFDEPOTBASE= # empty
Package Makefiles should refer to PKG_SYSCONFBASEDIR instead of PKG_SYSCONFBASE when they want PKG_SYSCONFDIR stripped of PKG_SYSCONFSUBDIR. This makes PKG_SYSCONFBASE=/etc work with pkgviews by installing all config files into /etc/packages/<pkg> instead of occasionally putting some directly into /etc. Also only create PKG_SYSCONFDIR if we're actually going to copy config files.
2003-09-05 13:34:25 +02:00
PKG_SYSCONFBASEDIR= ${PKG_SYSCONFBASE}
Set DFLT_PKG_SYSCONDIR to the location that PKG_SYSCONFDIR would have been set to if it hadn't been overridden by PKG_SYSCONFDIR.<pkg>. This can be used in /etc/mk.conf to re-override certain PKG_SYSCONFDIR.<pkg> in /etc/mk.conf from various package Makefiles, e.g. PKG_SYSCONFDIR.openssl= ${DFLT_PKG_SYSCONFDIR} PKG_SYSCONFDIR.tcp_wrappers= ${DFLT_PKG_SYSCONFDIR}
2004-03-29 08:49:04 +02:00
.else
. if !empty(PKG_SYSCONFBASE:M${PREFIX}) || \
!empty(PKG_SYSCONFBASE:M${PREFIX}/*)
Merge pkgviews-mk branch into the HEAD by running: cd pkgsrc/mk cvs update -Pd -A cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
2003-09-02 08:59:37 +02:00
PKG_SYSCONFDEPOTBASE= # empty
Package Makefiles should refer to PKG_SYSCONFBASEDIR instead of PKG_SYSCONFBASE when they want PKG_SYSCONFDIR stripped of PKG_SYSCONFSUBDIR. This makes PKG_SYSCONFBASE=/etc work with pkgviews by installing all config files into /etc/packages/<pkg> instead of occasionally putting some directly into /etc. Also only create PKG_SYSCONFDIR if we're actually going to copy config files.
2003-09-05 13:34:25 +02:00
PKG_SYSCONFBASEDIR= ${PKG_SYSCONFBASE}
Move the PKG_SYSCONFDIR logic below the definition of PKGNAME. PKGNAME is use to set PKGBASE, which is used in the name of the package-specific config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if PKGNAME wasn't explicitly set in the package, then the override would not work.
2001-11-28 20:55:31 +01:00
. else
Set DFLT_PKG_SYSCONDIR to the location that PKG_SYSCONFDIR would have been set to if it hadn't been overridden by PKG_SYSCONFDIR.<pkg>. This can be used in /etc/mk.conf to re-override certain PKG_SYSCONFDIR.<pkg> in /etc/mk.conf from various package Makefiles, e.g. PKG_SYSCONFDIR.openssl= ${DFLT_PKG_SYSCONFDIR} PKG_SYSCONFDIR.tcp_wrappers= ${DFLT_PKG_SYSCONFDIR}
2004-03-29 08:49:04 +02:00
PKG_SYSCONFDEPOTBASE= ${PKG_SYSCONFBASE}/${DEPOT_SUBDIR}
PKG_SYSCONFBASEDIR= ${PKG_SYSCONFDEPOTBASE}/${PKGNAME}
Move the PKG_SYSCONFDIR logic below the definition of PKGNAME. PKGNAME is use to set PKGBASE, which is used in the name of the package-specific config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if PKGNAME wasn't explicitly set in the package, then the override would not work.
2001-11-28 20:55:31 +01:00
. endif
.endif
Set DFLT_PKG_SYSCONDIR to the location that PKG_SYSCONFDIR would have been set to if it hadn't been overridden by PKG_SYSCONFDIR.<pkg>. This can be used in /etc/mk.conf to re-override certain PKG_SYSCONFDIR.<pkg> in /etc/mk.conf from various package Makefiles, e.g. PKG_SYSCONFDIR.openssl= ${DFLT_PKG_SYSCONFDIR} PKG_SYSCONFDIR.tcp_wrappers= ${DFLT_PKG_SYSCONFDIR}
2004-03-29 08:49:04 +02:00
.if empty(PKG_SYSCONFSUBDIR)
DFLT_PKG_SYSCONFDIR:= ${PKG_SYSCONFBASEDIR}
.else
DFLT_PKG_SYSCONFDIR:= ${PKG_SYSCONFBASEDIR}/${PKG_SYSCONFSUBDIR}
.endif
PKG_SYSCONFDIR= ${DFLT_PKG_SYSCONFDIR}
.if defined(PKG_SYSCONFDIR.${PKG_SYSCONFVAR})
PKG_SYSCONFDIR= ${PKG_SYSCONFDIR.${PKG_SYSCONFVAR}}
PKG_SYSCONFBASEDIR= ${PKG_SYSCONFDIR.${PKG_SYSCONFVAR}}
PKG_SYSCONFDEPOTBASE= # empty
.endif
Allow a package to specify the ownership and permission on ${PKG_SYSCONFDIR} if PKG_SYSCONFSUBDIR is defined and non-empty. A package may now set PKG_SYSCONFDIR_PERMS to an "owner group mode" triplet, which defaults to "${ROOT_USER} ${ROOT_GROUP} 755".
2006-04-26 07:58:44 +02:00
PKG_SYSCONFDIR_PERMS?= ${ROOT_USER} ${ROOT_GROUP} 755
Move the PKG_SYSCONFDIR logic below the definition of PKGNAME. PKGNAME is use to set PKGBASE, which is used in the name of the package-specific config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if PKGNAME wasn't explicitly set in the package, then the override would not work.
2001-11-28 20:55:31 +01:00
Visual cleanup from tv-derecurse: Consolidate many MAKE_ENVs and SCRIPTS_ENVs into a common block. (CONFIGURE_ENVs to be done later.) Introduce new variable ALL_ENV which is automatically included into all of MAKE_ENV, SCRIPTS_ENV, and CONFIGURE_ENV; this allows much cleaner addition of the common CC/CXX/CFLAGS/etc. variables needed by all of these.
2005-02-11 17:36:49 +01:00
ALL_ENV+= PKG_SYSCONFDIR=${PKG_SYSCONFDIR:Q}
Introduce a new variable "CONF_DEPENDS" for pkgviews: a package's config directory matches the config directory for the dependency listed in CONF_DEPENDS. Use symlinks to physically point the package's config directory to the dependency's config directory, and handle all of this in the INSTALL/DEINSTALL scripts. Also make the INSTALL/DEINSTALL scripts a bit smarter about not copying files and not removing files if the source and destination file locations point to the same thing.
2003-09-17 04:38:22 +02:00
BUILD_DEFS+= PKG_SYSCONFBASEDIR PKG_SYSCONFDIR
Move the PKG_SYSCONFDIR logic below the definition of PKGNAME. PKGNAME is use to set PKGBASE, which is used in the name of the package-specific config directory override (PKG_SYSCONFDIR.${PKGBASE}). Prior to this, if PKGNAME wasn't explicitly set in the package, then the override would not work.
2001-11-28 20:55:31 +01:00
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
# These are all of the tools use by pkgsrc Makefiles. This should
# eventually be split up into lists of tools required by different
# phases of a pkgsrc build.
#
Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by making 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-07-15 20:27:48 +02:00
USE_TOOLS+= \
We only need "date" to write the date into the +PRESERVE file.
2005-05-16 06:48:05 +02:00
[ awk basename cat chgrp chmod chown cmp cp cut dirname echo \
egrep env false file find grep head hostname id install ln ls \
No package seems to be using ${NICE} so don't require it.
2005-05-16 07:11:51 +02:00
mkdir mv pax pwd rm rmdir sed sh sort tail test touch tr true \
wc xargs
tsort is only used by bsd.bulk-pkg.mk.
2005-05-16 06:30:41 +02:00
* Add a new stage "bootstrap-depends" that happens before all other stages, and that installs dependencies listed in BOOTSTRAP_DEPENDS. The bootstrap-depends step works just like the normal depends step and honors the value of DEPENDS_TARGET. It's now possible to add dependencies solely to facilitate fetching the distfiles, e.g. BOOTSTRAP_DEPENDS+= curl-[0-9]*:../../www/curl * Teach the tools framework about ":bootstrap" as a tools modifier which indicates the tool should be added as a dependency via BOOTSTRAP_DEPENDS. * Add "digest" to the tools framework. * Use USE_TOOLS+=digest:bootstrap to force pkgsrc to install digest before anything else. Get rid of unused "uptodate-digest" target and related digest version-checking code. * Finish the refactoring work: split checksum-related code out of bsd.pkg.mk and into pkgsrc/mk/checksum and replace the "checksum" target command list with a script that does all the real work. * Make DIGEST_ALGORITHMS and PATCH_DIGEST_ALGORITHM into private variables by prepending them with an underscore. Also, rename _PATCH_DIGEST_ALGORITHM to _PATCH_DIGEST_ALGORITHMS and adjust the makepatchsum target to allow that variable to contain a list of algorithms, all of which are used when creating the patch checksums for ${DISTINFO_FILE}.
2006-07-13 16:02:34 +02:00
USE_TOOLS+= ${NO_CHECKSUM:D:Udigest\:bootstrap}
Fix mistake in previous commit -- expr is required by the wrapper framework. Problem & fix from tron@.
2005-05-16 17:20:15 +02:00
# bsd.wrapper.mk
Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by making 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-07-15 20:27:48 +02:00
USE_TOOLS+= expr
Fix mistake in previous commit -- expr is required by the wrapper framework. Problem & fix from tron@.
2005-05-16 17:20:15 +02:00
tee is only used by bsd.bulk-pkg.mk.
2005-05-16 06:54:11 +02:00
# bsd.bulk-pkg.mk uses certain tools
tsort is only used by bsd.bulk-pkg.mk.
2005-05-16 06:30:41 +02:00
.if defined(BATCH)
Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by making 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-07-15 20:27:48 +02:00
USE_TOOLS+= tee tsort
tsort is only used by bsd.bulk-pkg.mk.
2005-05-16 06:30:41 +02:00
.endif
We only need mtree if NO_MTREE isn't defined.
2005-05-16 02:11:50 +02:00
Use ${SLEEP} instead of sleep, and note that we use the sleep tool if we're doing locking.
2005-11-04 21:06:14 +01:00
# We need shlock and sleep if we're using locking to synchronize multiple
# builds over the same pkgsrc tree.
Consolidate the bits that add to PKGSRC_USE_TOOLS, and improve the comment for shlock.
2005-05-16 02:00:35 +02:00
#
.if ${PKGSRC_LOCKTYPE} != "none"
Use ${SLEEP} instead of sleep, and note that we use the sleep tool if we're doing locking.
2005-11-04 21:06:14 +01:00
USE_TOOLS+= shlock sleep
Consolidate the bits that add to PKGSRC_USE_TOOLS, and improve the comment for shlock.
2005-05-16 02:00:35 +02:00
.endif
Finish removing instances of _USE_NEW_TOOLS from pkgsrc.
2005-05-22 22:15:40 +02:00
# Tools
Add a new yes/no variable USE_NEW_TOOLS to ease testing the new tools framework. USE_NEW_TOOLS defaults to "no".
2005-04-15 04:04:57 +02:00
.include "../../mk/tools/bsd.tools.mk"
Move the inclusion of tools.mk ahead of bsd.buildlink3.mk so that tools.mk can include buildlink3.mk files. This change also causes work/.tools/bin to appear after work/.buildlink/bin in the PATH, but we never relied on this behaviour, so this side-effect should have no impact.
2004-04-27 21:23:34 +02:00
Fix previous... instead of moving bsd.pkg.barrier.mk down below .MAIN, move .MAIN all the way to the top of the file. bsd.pkg.barrier.mk (currently) needs to be included before bsd.wrapper.mk since it defines _BARRIER_COOKIE, which is expanded and used in place within bsd.wrapper.mk. This makes the "wrapper" phase run again.
2006-07-06 18:58:17 +02:00
# Barrier
.include "../../mk/bsd.pkg.barrier.mk"
Simplify unprivileged builds by adding a new variable, UNPRIVILEGED, that, when set to YES, changes multiple defaults to let this work properly.
2005-05-29 19:12:15 +02:00
# Unprivileged builds
.include "../../mk/unprivileged.mk"
compiler.mk uses the following tools to compute the values of variables at the time that they're defined: ${AWK}, ${GREP}, ${SED}, ${TRUE}. Move the inclusion of compiler.mk below the inclusion of bsd.tools.mk so that these variables are properly defined by the time they are used. This should fix problems where pkgsrc gcc was not being properly detected when using the new tools framework. This change has the side effect of changing the relative order of the compiler directories and the tool directory in the PATH, but this has no impact on existing packages, and actually makes more sense anyway.
2005-05-14 08:04:44 +02:00
# If NO_BUILD is defined, default to not needing a compiler.
.if defined(NO_BUILD)
USE_LANGUAGES?= # empty
.endif
# Get the proper dependencies and set the PATH to use the compiler
# named in PKGSRC_COMPILER.
#
.include "../../mk/compiler.mk"
Always include wrapper/bl3, period, even if NO_BUILD.
2005-04-05 16:00:33 +02:00
.include "../../mk/wrapper/bsd.wrapper.mk"
Merge pkgsrc/mk from the buildlink2 branch back into the main trunk.
2002-08-22 10:21:26 +02:00
If USE_ABI_DEPENDS=no, do not add the BUILDLINK_ABI_DEPENDS.$pkg to BUILD_DEPENDS. (I posted about this to pkgsrc-users on April 14.)
2006-05-06 05:28:44 +02:00
.if defined(ABI_DEPENDS) || defined(BUILD_ABI_DEPENDS)
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
. if !empty(USE_ABI_DEPENDS:M[yY][eE][sS])
DEPENDS+= ${ABI_DEPENDS}
If USE_ABI_DEPENDS=no, do not add the BUILDLINK_ABI_DEPENDS.$pkg to BUILD_DEPENDS. (I posted about this to pkgsrc-users on April 14.)
2006-05-06 05:28:44 +02:00
BUILD_DEPENDS+= ${BUILD_ABI_DEPENDS}
Process RECOMMENDED *after* including bsd.buildlink3.mk; else it has no real effect at all.
2004-08-24 02:27:13 +02:00
. else
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
BUILD_DEFS+= USE_ABI_DEPENDS
Process RECOMMENDED *after* including bsd.buildlink3.mk; else it has no real effect at all.
2004-08-24 02:27:13 +02:00
. endif
.endif
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
# Find out the PREFIX of dependencies where the PREFIX is needed at build time.
.if defined(EVAL_PREFIX)
Instead of structuring code so that variables defined by the EVAL_PREFIX loop are only used afterwards, split out the EVAL_PREFIX code into a separate file find-prefix.mk that can be included at any point to generate a prefix-computation for the variables specified by FIND_PREFIX at the inclusion point.
2005-05-12 22:41:10 +02:00
FIND_PREFIX:= ${EVAL_PREFIX}
. include "../../mk/find-prefix.mk"
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
.endif
.if !defined(_PATH_ORIG)
_PATH_ORIG:= ${PATH}
MAKEFLAGS+= _PATH_ORIG=${_PATH_ORIG:Q}
Fix handling of PREPEND_PATH in dependency-recursed builds.
2005-01-27 12:21:46 +01:00
.endif
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
Rewrote the _PATH_CMD command, which could not handle a PATH environment variable before if it had multiple adjacent white-space characters in it. Removed the dependency on awk(1), as a simple shell script can do this job, too. Another change is that all kinds of weird pathnames can be used for PREPEND_PATH, like /bin, "/bin/Program Files", "/ ", /foo\ bar, and so on. This had not been possible before, too. Related to PR 32079. Ok'ed by jlam.
2005-11-15 22:21:01 +01:00
.if !empty(PREPEND_PATH:M*)
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
# This is very Special. Because PREPEND_PATH is set with += in reverse order,
Rewrote the _PATH_CMD command, which could not handle a PATH environment variable before if it had multiple adjacent white-space characters in it. Removed the dependency on awk(1), as a simple shell script can do this job, too. Another change is that all kinds of weird pathnames can be used for PREPEND_PATH, like /bin, "/bin/Program Files", "/ ", /foo\ bar, and so on. This had not been possible before, too. Related to PR 32079. Ok'ed by jlam.
2005-11-15 22:21:01 +01:00
# this command reverses the order again (since bootstrap bmake doesn't
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
# yet support the :[-1..1] construct).
Rewrote the _PATH_CMD command, which could not handle a PATH environment variable before if it had multiple adjacent white-space characters in it. Removed the dependency on awk(1), as a simple shell script can do this job, too. Another change is that all kinds of weird pathnames can be used for PREPEND_PATH, like /bin, "/bin/Program Files", "/ ", /foo\ bar, and so on. This had not been possible before, too. Related to PR 32079. Ok'ed by jlam.
2005-11-15 22:21:01 +01:00
_PATH_CMD= \
path=${_PATH_ORIG:Q}; \
for i in ${PREPEND_PATH}; do path="$$i:$$path"; done; \
${ECHO} "$$path"
PATH= ${_PATH_CMD:sh} # DOES NOT use :=, to defer evaluation
Merge down deferred PREPEND_PATH handling from the tv-derecurse branch. Also merge in deferred CLASSPATH handling, which can now be moved back to java-vm.mk for cleanliness.
2005-01-24 20:32:33 +01:00
.endif
* Move pkgsrc/mk/compiler/bsd.compiler.mk to pkgsrc/mk/compiler.mk. Package Makefiles may now directly include compiler.mk. * Don't include compiler.mk within bsd.prefs.mk any longer. It was only included for the purposes of defining CC_VERSION. Packages that want to test the value of CC_VERSION should now first include "../../mk/compiler.mk". Any GCC_REQD statements in package Makefiles should be set before compiler.mk is included. * Simpllfy pkgsrc/mk/compiler/*.mk files as a result of not needing to be included indirectly by bsd.prefs.mk. We remove the special handling associated with detecting whether the file was included from within bsd.prefs.mk. These files are now much more straightforward to write and understand. * G/C the BSD_PREFS_MK stack mechanism as the only users (compiler/*) no longer need it. * Ensure that directories are prepended to the PATH only from within bsd.pkg.mk.
2004-02-18 14:32:38 +01:00
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
################################################################
This is NetBSD. s/port/package/g
1999-08-10 12:48:23 +02:00
# Many ways to disable a package.
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
#
Revert last change. I only tested this on netbsd-1-4; it doesn't seem to work on netbsd-1-5 at all.
2000-09-07 04:29:40 +02:00
# Ignore packages that can't be resold if building for a CDROM.
Introduce a new category, "crypto", with a special property: If the user sets MKCRYPTO=no, packages in this category won't be fetched, installed, built, or packaged. Also, binary package users forbidden, by law, from using strong cryptography would presumably find the list on the category's automatically generated web page useful for ensuring compliance.
2000-09-06 22:28:32 +02:00
#
Correct a factual error in the comment "ways to disable a package": we actually check for "X", and not just Motif. Also, clean up word wrap, and rearrange the sections to be in the same order as the checks they refer to.
2000-09-07 17:26:52 +02:00
# Don't build a package if it's restricted and we don't want to
# get into that.
#
Add a new mechanism for handling "crypto" packages, as discussed on tech-pkg. Setting either USE_SSL or CRYPTO in the package's Makefile will permit the package to build or not, depending on the setting of MKCRYPTO (set to yes by default).
2000-09-09 20:45:16 +02:00
# Don't build any package that utilizes strong cryptography, for
# when the law of the land forbids it.
#
Correct a factual error in the comment "ways to disable a package": we actually check for "X", and not just Motif. Also, clean up word wrap, and rearrange the sections to be in the same order as the checks they refer to.
2000-09-07 17:26:52 +02:00
# Don't attempt to build packages against X if we don't have X.
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
#
This is NetBSD. s/port/package/g
1999-08-10 12:48:23 +02:00
# Don't build a package if it's broken.
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
################################################################
* Garbage collect IGNORE -> SKIP migration. * {NOT,ONLY}_FOR_PLATHOME mismatch is not an error. Set PKG_SKIP_REASON for those cases. This makes bulk builds happier.
2002-12-27 07:53:42 +01:00
.if !defined(NO_SKIP)
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. if (defined(NO_BIN_ON_CDROM) && defined(FOR_CDROM))
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
PKG_FAIL_REASON+= "${PKGNAME} may not be placed in binary form on a CDROM:" \
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
" "${NO_BIN_ON_CDROM:Q}
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
. if (defined(NO_SRC_ON_CDROM) && defined(FOR_CDROM))
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
PKG_FAIL_REASON+= "${PKGNAME} may not be placed in source form on a CDROM:" \
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
" "${NO_SRC_ON_CDROM:Q}
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
. if (defined(RESTRICTED) && defined(NO_RESTRICTED))
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
PKG_FAIL_REASON+= "${PKGNAME} is restricted:" \
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
" "${RESTRICTED:Q}
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
. if !(${MKCRYPTO} == "YES" || ${MKCRYPTO} == yes)
Deprecate USE_SSL.
2002-07-02 17:25:49 +02:00
. if defined(CRYPTO)
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
PKG_FAIL_REASON+= "${PKGNAME} may not be built, because it utilizes strong cryptography"
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
Add a new mechanism for handling "crypto" packages, as discussed on tech-pkg. Setting either USE_SSL or CRYPTO in the package's Makefile will permit the package to build or not, depending on the setting of MKCRYPTO (set to yes by default).
2000-09-09 20:45:16 +02:00
. endif
Remove the commands that tried to make the ${X11BASE} directory if it didn't exist. Those commands were never run anyway, but moving the .MAIN target exposed these commands as unassociated.
2006-07-07 17:59:06 +02:00
. if defined(USE_X11) && (${X11_TYPE} == "native") && !exists(${X11BASE})
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
PKG_FAIL_REASON+= "${PKGNAME} uses X11, but ${X11BASE} not found"
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
. if defined(BROKEN)
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
PKG_FAIL_REASON+= "${PKGNAME} is marked as broken:" ${BROKEN:Q}
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. if defined(LICENSE)
Collapse two .for blocks to improve readability: _ULIMIT_CMD to use a ${...:@var@loop ...@} construct _ACCEPTABLE to use a !empty(var:Mfoo) conditional
2005-11-18 18:07:13 +01:00
. if defined(ACCEPTABLE_LICENSES) && !empty(ACCEPTABLE_LICENSES:M${LICENSE})
Add an ACCEPTABLE_LICENCES definition to /etc/mk.conf. This is a whitespace-delimited list, and details which types of licences are allowed. Package Makefiles with non-standard licences (shareware, non-commercial-use only) should have a LICENCE= <type> added. Normal package Makefiles remain unchanged. Add logic to bsd.pkg.mk to check, if LICENCE is defined, that the package is acceptable.
1998-07-06 17:10:48 +02:00
_ACCEPTABLE= yes
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif # ACCEPTABLE_LICENSES
Found another two uses of .ifndef and .ifdef. Converted them to .if [!]defined().
2005-05-14 04:03:00 +02:00
. if !defined(_ACCEPTABLE)
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
PKG_FAIL_REASON+= "${PKGNAME} has an unacceptable license: ${LICENSE}." \
Update the wording a bit when a license is not accepted, to better indicate the proper process: first read the license, then accept, and indicate so in /etc/mk.conf: yui% make ===> graphviz-1.12 has an unacceptable license: graphviz-license. ===> To view the license, enter "/usr/bin/make show-license". ===> To indicate acceptance, add this line to your /etc/mk.conf: ===> ACCEPTABLE_LICENSES+=graphviz-license *** Error code 1
2004-10-01 02:23:18 +02:00
" To view the license, enter \"${MAKE} show-license\"." \
" To indicate acceptance, add this line to your /etc/mk.conf:" \
" ACCEPTABLE_LICENSES+=${LICENSE}"
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif # _ACCEPTABLE
. endif # LICENSE
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
Move all settings of IGNORE into one spot. No need for the arch-checking code (ONLY_FOR_PLATFORM, NOT_FOR_PLATFORM) to be located elsewhere. Inspired by OpenBSD.
2000-05-31 00:36:53 +02:00
# Define __PLATFORM_OK only if the OS matches the pkg's allowed list.
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. if defined(ONLY_FOR_PLATFORM) && !empty(ONLY_FOR_PLATFORM)
. for __tmp__ in ${ONLY_FOR_PLATFORM}
. if ${MACHINE_PLATFORM:M${__tmp__}} != ""
Move all settings of IGNORE into one spot. No need for the arch-checking code (ONLY_FOR_PLATFORM, NOT_FOR_PLATFORM) to be located elsewhere. Inspired by OpenBSD.
2000-05-31 00:36:53 +02:00
__PLATFORM_OK?= yes
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif # MACHINE_PLATFORM
. endfor # __tmp__
. else # !ONLY_FOR_PLATFORM
__PLATFORM_OK?= yes
. endif # ONLY_FOR_PLATFORM
. for __tmp__ in ${NOT_FOR_PLATFORM}
. if ${MACHINE_PLATFORM:M${__tmp__}} != ""
. undef __PLATFORM_OK
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
. endif # MACHINE_PLATFORM
. endfor # __tmp__
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. if !defined(__PLATFORM_OK)
* Garbage collect IGNORE -> SKIP migration. * {NOT,ONLY}_FOR_PLATHOME mismatch is not an error. Set PKG_SKIP_REASON for those cases. This makes bulk builds happier.
2002-12-27 07:53:42 +01:00
PKG_SKIP_REASON+= "${PKGNAME} is not available for ${MACHINE_PLATFORM}"
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif # !__PLATFORM_OK
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
#
# Now print some error messages that we know we should ignore the pkg
#
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
. if defined(PKG_FAIL_REASON) || defined(PKG_SKIP_REASON)
The new target do-check-pkg-fail-reason should to be a dependency of every top level target that is intended to be called by the user or by a package different from the current package. It provides the same action as the "main" targets like "fetch", "expand", "build" before in case PKG_FAIL_REASON is set, that is it prints all PKG_FAIL_REASONs and fails. Fixes PR 32202. Implementation notes: - The target names have the "do-" prefix to not pollute the bsd.pkg.check.mk namespace. - The PKG_SKIP_REASON has no influence on the do-check-pkg-fail-reason target, although both are handled with the same code.
2005-12-01 01:17:05 +01:00
.PHONY: do-check-pkg-fail-or-skip-reason
do not check for ACCEPTABLE_LICENCES when deinstalling. closes PR pkg/13211
2001-06-19 13:54:56 +02:00
fetch checksum extract patch configure all build install package \
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
update depends do-check-pkg-fail-or-skip-reason:
* Garbage collect IGNORE -> SKIP migration. * {NOT,ONLY}_FOR_PLATHOME mismatch is not an error. Set PKG_SKIP_REASON for those cases. This makes bulk builds happier.
2002-12-27 07:53:42 +01:00
. if defined(SKIP_SILENT)
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
@${DO_NADA}
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. else
Fixed the test on PKG_{FAIL,SKIP}_REASON. Added a prefix line to the output of PKG_SKIP_REASON, since the plain message does not say where it comes from.
2006-07-06 01:27:34 +02:00
. if defined(PKG_FAIL_REASON) && !empty(PKG_FAIL_REASON:M*)
Output PKG_{FAIL,SKIP}_REASON messages to standard error instead of standard output. These are error or warning messages, so they shouldn't be "seen" by anything expecting the output of a "make" command to make sense. This addresses PR pkg/32239 by following the suggestions by Roland Illig.
2006-06-15 04:39:19 +02:00
@for str in ${PKG_FAIL_REASON}; do \
${ERROR_MSG} "$$str"; \
done
Fixed the test on PKG_{FAIL,SKIP}_REASON. Added a prefix line to the output of PKG_SKIP_REASON, since the plain message does not say where it comes from.
2006-07-06 01:27:34 +02:00
. endif
. if defined(PKG_SKIP_REASON) && !empty(PKG_SKIP_REASON:M*)
@${WARNING_MSG} "Skipping ${PKGNAME}:"; \
for str in ${PKG_SKIP_REASON}; do \
Output PKG_{FAIL,SKIP}_REASON messages to standard error instead of standard output. These are error or warning messages, so they shouldn't be "seen" by anything expecting the output of a "make" command to make sense. This addresses PR pkg/32239 by following the suggestions by Roland Illig.
2006-06-15 04:39:19 +02:00
${WARNING_MSG} "$$str"; \
* Prevent " etc. in RESTRICTED (NO_{SRC,BIN}_ON_{CDROM,FTP}) and BROKEN from producing errors * Rework IGNORE handling: - IGNORE messages must now include the pkg's name - if multiple reasons exist for a pkg to be ignored, they are now all printed - IGNORECMD is gone * Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is set (I really don't want to see that list every day!) * Catch one leftover 'depends' -> 'install-depends'
2000-08-19 17:32:15 +02:00
done
Fixed the test on PKG_{FAIL,SKIP}_REASON. Added a prefix line to the output of PKG_SKIP_REASON, since the plain message does not say where it comes from.
2006-07-06 01:27:34 +02:00
. endif
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
Fixed the test on PKG_{FAIL,SKIP}_REASON. Added a prefix line to the output of PKG_SKIP_REASON, since the plain message does not say where it comes from.
2006-07-06 01:27:34 +02:00
. if defined(PKG_FAIL_REASON) && !empty(PKG_FAIL_REASON:M*)
Replace IGNORE into PKG_FAIL_REASON and PKG_SKIP_REASON, so pkgsrc can stop builds when a dependency is broken, yet continue builds when a dependency is merely skipped (usually because it duplicates functionality in the base system). Thus IGNORE_FAIL, the oft-misunderstood and naught-documented option, goes away. This addresses many people's complaints on tech-pkg@ and other lists, as well as PR pkg/18157.
2002-12-07 03:37:56 +01:00
@${FALSE}
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. endif
* Garbage collect IGNORE -> SKIP migration. * {NOT,ONLY}_FOR_PLATHOME mismatch is not an error. Set PKG_SKIP_REASON for those cases. This makes bulk builds happier.
2002-12-27 07:53:42 +01:00
. endif # SKIP
.endif # !NO_SKIP
Re-move .if!defined(__ARCH_OK) to fix use of NO_IGNORE; document some .endif's
1998-01-25 15:46:10 +01:00
The new target do-check-pkg-fail-reason should to be a dependency of every top level target that is intended to be called by the user or by a package different from the current package. It provides the same action as the "main" targets like "fetch", "expand", "build" before in case PKG_FAIL_REASON is set, that is it prints all PKG_FAIL_REASONs and fails. Fixes PR 32202. Implementation notes: - The target names have the "do-" prefix to not pollute the bsd.pkg.check.mk namespace. - The PKG_SKIP_REASON has no influence on the do-check-pkg-fail-reason target, although both are handled with the same code.
2005-12-01 01:17:05 +01:00
.PHONY: do-check-pkg-fail-reason
do-check-pkg-fail-reason:
@${DO_NADA}
# This target should appear as a dependency of every top level target that
# is intended to be called by the user or by a package different from the
# current package.
.if defined(PKG_FAIL_REASON)
do-check-pkg-fail-reason: do-check-pkg-fail-or-skip-reason
.endif
+ Add and document the PKG_RELATIVE_SYMLINKS option, which makes sure that a symbolic link in a package is relative to ${PREFIX}, if it is under ${PREFIX}, using the -l argument to pkg_create. + Build a +BUILD_INFO file with appropriate information from the package build. Thanks to Christoph Badura for pointers to the appropriate information.
1998-10-20 18:01:03 +02:00
# Add these defs to the ones dumped into +BUILD_DEFS
* Make sure PKGPATH gets added to BUILD_DEFS (I thought it was there for a long time. Oh well.) * Only replace the value of PATH for "PATH", not any variable whose name starts with PATH (like PKGPATH :-) Hinted by Jason R. Mastaler <jason@mastaler.com> on tech-pkg.
2000-11-27 23:24:49 +01:00
BUILD_DEFS+= PKGPATH
+ Add and document the PKG_RELATIVE_SYMLINKS option, which makes sure that a symbolic link in a package is relative to ${PREFIX}, if it is under ${PREFIX}, using the -l argument to pkg_create. + Build a +BUILD_INFO file with appropriate information from the package build. Thanks to Christoph Badura for pointers to the appropriate information.
1998-10-20 18:01:03 +02:00
BUILD_DEFS+= OPSYS OS_VERSION MACHINE_ARCH MACHINE_GNU_ARCH
make sure FFLAGS ends up in MAKE_ENV as well as BUILD_DEFS. This allows you to do make FFLAGS='-my -f -flags' and at least the pkgs which obey FFLAGS use them.
2002-01-22 19:15:20 +01:00
BUILD_DEFS+= CPPFLAGS CFLAGS FFLAGS LDFLAGS
Add 'RESTRICTED' to ${BUILD_DEFS}, so that any restrictions are recorded in the binary package.
2000-07-23 20:42:48 +02:00
BUILD_DEFS+= OBJECT_FMT LICENSE RESTRICTED
* Replace MIRROR_DISTFILES with NO_SRC_ON_FTP * Replace NO_CDROM with NO_SRC_ON_CDROM and NO_BIN_ON_CDROM * Add NO_{SRC,BIN}_ON_{FTP,CDROM} to BUILD_DEFS (in case someone wants to re-distribute a binary pkg, so he has a chance to know about resitrictions) * Adjust 'mirror-distfiles' target for NO_SRC_ON_FTP
2000-08-19 00:43:19 +02:00
BUILD_DEFS+= NO_SRC_ON_FTP NO_SRC_ON_CDROM
BUILD_DEFS+= NO_BIN_ON_FTP NO_BIN_ON_CDROM
+ Add and document the PKG_RELATIVE_SYMLINKS option, which makes sure that a symbolic link in a package is relative to ${PREFIX}, if it is under ${PREFIX}, using the -l argument to pkg_create. + Build a +BUILD_INFO file with appropriate information from the package build. Thanks to Christoph Badura for pointers to the appropriate information.
1998-10-20 18:01:03 +02:00
add OSVERSION_SPECIFIC to BUILD_DEFS if defined so it ends up in the binary package. This way we can look at a binary package and determine what versions of the OS it may run on.
2001-07-07 19:10:36 +02:00
.if defined(OSVERSION_SPECIFIC)
BUILD_DEFS+= OSVERSION_SPECIFIC
.endif # OSVERSION_SPECIFIC
Mark all targets that do not correspond to real files with the .PHONY attribute.
2003-07-24 00:02:48 +02:00
.PHONY: all
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
.if !target(all)
Due to the special handling of pkgtools/digest in pkgsrc (it must be installed before the normal dependency checks), on a system without any packages installed, we can run into the problem where digest won't install because it has already been installed as part of installing a build dependency. This can happen if, e.g., PKGSRC_COMPILER is set to "ccache gcc", and you try to build devel/gmake. Change the way that the uptodate-digest target installs pkgtools/digest by ensuring that pkgtools/digest is deinstalled just before installing it.
2004-03-22 05:07:15 +01:00
all: ${_PKGSRC_BUILD_TARGETS}
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
.endif
################################################################
# More standard targets start here.
#
# These are the body of the build/install framework. If you are
# not happy with the default actions, and you can't solve it by
# adding pre-* or post-* targets/scripts, override these.
################################################################
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
# acquire-lock, release-lock are .USE macro targets for acquiring and
# release coarse-grained locks.
#
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
_LOCKFILE= ${WRKDIR}/.lockfile
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
acquire-lock: .USE
Add coarse-grained locking to pkgsrc builds, by means of a beefed up version of the bare-bones code in PR 7590, from David Maxwell. The definition governing the type of locking used is PKGSRC_LOCKTYPE, which can take any of the values "none", "sleep", and "once". The default is "none". If "sleep" locking is used, and process A is building a package, when process B attempts to build the same package, process B will sleep for PKGSRC_SLEEPSECS seconds, and attempt to grab the lock again. Coarse-grained locking uses the OBJHOSTNAME definition to ensure that the PID space is regular for shlock(1) to do its work. The pkgsrc/pkgtools/shlock package has been provided for environments where shlock is not standard.
2002-01-19 22:29:41 +01:00
.if ${PKGSRC_LOCKTYPE} == "none"
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
@${DO_NADA}
Add coarse-grained locking to pkgsrc builds, by means of a beefed up version of the bare-bones code in PR 7590, from David Maxwell. The definition governing the type of locking used is PKGSRC_LOCKTYPE, which can take any of the values "none", "sleep", and "once". The default is "none". If "sleep" locking is used, and process A is building a package, when process B attempts to build the same package, process B will sleep for PKGSRC_SLEEPSECS seconds, and attempt to grab the lock again. Coarse-grained locking uses the OBJHOSTNAME definition to ensure that the PID space is regular for shlock(1) to do its work. The pkgsrc/pkgtools/shlock package has been provided for environments where shlock is not standard.
2002-01-19 22:29:41 +01:00
.else
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
@if ${TEST} ! -x ${SHLOCK:Q}""; then \
${ERROR_MSG} "The ${SHLOCK:Q} utility does not exist, and is necessary for locking."; \
${ERROR_MSG} "Please \""${MAKE:Q}" install\" in ../../pkgtools/shlock."; \
exit 1; \
fi
. if !defined(OBJHOSTNAME)
@${ERROR_MSG} "PKGSRC_LOCKTYPE needs OBJHOSTNAME defined."; \
exit 1
. endif
${_PKG_SILENT}${_PKG_DEBUG}set -e; \
When setting up the lockfile, don't store whitespace printed by ps(1), so that % make ===> do-fetch [digest-20021220] ===> Checking for vulnerabilities in digest-20021220 => Lock acquired on behalf of process 356 => Lock released on behalf of process 356 becomes % make ===> do-fetch [digest-20021220] ===> Checking for vulnerabilities in digest-20021220 => Lock acquired on behalf of process 814 => Lock released on behalf of process 814
2003-06-14 18:53:00 +02:00
ppid=`${PS} -p $$$$ -o ppid | ${AWK} 'NR == 2 { print $$1 }'`; \
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
if ${TEST} -z "$$ppid"; then \
${ERROR_MSG} "No parent process ID found."; \
exit 1; \
catch locking failure case where we couldn't find the parent's process ID. from Roland Illig.
2004-07-04 00:11:56 +02:00
fi; \
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
while ${TRUE}; do \
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
if ${TEST} -f /var/run/dmesg.boot -a -f ${_LOCKFILE}; then \
rebooted=`${FIND} /var/run/dmesg.boot -newer ${_LOCKFILE} -print`; \
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
if ${TEST} -n "$$rebooted"; then \
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
${STEP_MSG} "Removing stale ${_LOCKFILE}"; \
${RM} -f ${_LOCKFILE}; \
Don't use the -nt operator for ${TEST}. It is not defined in POSIX, and not provided by the Solaris 9 /bin/sh. Use the find(1) -newer expression instead, as it expresses exactly what we want, compared to the "ls -t" hack.
2005-02-12 01:27:41 +01:00
fi; \
Check that the lockfile isn't stale from being left over across a system reboot by testing whether or not /var/run/dmesg.boot is newer than it or not. Fix suggested by agc@NetBSD.org and simonb@NetBSD.org.
2003-09-09 13:00:30 +02:00
fi; \
Ensure the directory containing the lockfile is created prior to the lockfile's creation. Fixes the "depends" step when PKGSRC_LOCKTYPE is not "none".
2006-06-05 04:22:49 +02:00
${MKDIR} ${_LOCKFILE:H}; \
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
if ${SHLOCK} -f ${_LOCKFILE} -p $$ppid; then \
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
break; \
fi; \
case ${PKGSRC_LOCKTYPE:Q}"" in \
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
once) ${ERROR_MSG} "Lock is held by pid `${CAT} ${_LOCKFILE}`"; \
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
exit 1; \
;; \
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
sleep) ${STEP_MSG} "Lock is held by pid `${CAT} ${_LOCKFILE}`"; \
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
${SLEEP} ${PKGSRC_SLEEPSECS}; \
;; \
esac; \
done
. if defined(PKG_VERBOSE)
Make it a little easier to read the lock/unlock output by inserting some quotes.
2006-07-06 23:59:38 +02:00
@${STEP_MSG} "Lock acquired for \`\`${.TARGET:S/^acquire-//:S/-lock$//}'' on behalf of process `${CAT} ${_LOCKFILE}`"
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
. endif
.endif
Add coarse-grained locking to pkgsrc builds, by means of a beefed up version of the bare-bones code in PR 7590, from David Maxwell. The definition governing the type of locking used is PKGSRC_LOCKTYPE, which can take any of the values "none", "sleep", and "once". The default is "none". If "sleep" locking is used, and process A is building a package, when process B attempts to build the same package, process B will sleep for PKGSRC_SLEEPSECS seconds, and attempt to grab the lock again. Coarse-grained locking uses the OBJHOSTNAME definition to ensure that the PID space is regular for shlock(1) to do its work. The pkgsrc/pkgtools/shlock package has been provided for environments where shlock is not standard.
2002-01-19 22:29:41 +01:00
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
release-lock: .USE
.if ${PKGSRC_LOCKTYPE} == "none"
@${DO_NADA}
.else
. if defined(PKG_VERBOSE)
Make it a little easier to read the lock/unlock output by inserting some quotes.
2006-07-06 23:59:38 +02:00
@${STEP_MSG} "Lock released for \`\`${.TARGET:S/^release-//:S/-lock$//}'' on behalf of process `${CAT} ${_LOCKFILE}`"
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
. endif
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
${_PKG_SILENT}${_PKG_DEBUG}${RM} -f ${_LOCKFILE}
Drop the use of _ACQUIRE_LOCK and _RELEASE_LOCK and replace with acquire-lock and release-lock macro targets. Take advantage of using a make target by breaking up the _ACQUIRE_LOCK script into smaller pieces, and make better use of the *_MSG definitions for printing messages within the acquire-lock and release-lock targets.
2006-06-04 06:31:47 +02:00
.endif
Add a MIRROR_DISTFILE variable; defaults to "yes", and should be set to "no" in a package's Makefile when the authors have placed restrictions on the redistribution of the distfiles. (Thanks to Jason Thorpe for the idea). Add a `mirror' target, which will do a "make fetch" if the package's distfile is allowed to be redistributed. This is for use on sites which mirror package distfiles. (Thanks to Charles Hannum for the idea).
1998-01-22 11:20:48 +01:00
Introduce "makedirs" as a helper target to create directories with unprivileged ownership.
2006-06-08 18:21:51 +02:00
.PHONY: makedirs
makedirs: ${WRKDIR}
* Turn _SHELL_EXTRACT into a "subroutine" for extracting an archive. It extracts the contents of archive named by the shell variable "extract_file" based on the file extension of the archive. The contents are dumped into the current directory. * Unify the EXTRACT_CMD handling. We now define the default EXTRACT_CMD to be ${_SHELL_EXTRACT} (see above). Otherwise, if it's already defined in the package Makefile, then that EXTRACT_CMD is used to extract all of the archives. * Rearrange the locking code so that it's localized instead of interspersed in the extraction code. * Add EXTRACT_CMD definitions for files that are only compressed (foo.c.gz) that decompress the file into ${WRKDIR}.
2002-02-25 05:43:55 +01:00
${WRKDIR}:
.if !defined(KEEP_WRKDIR)
. if ${PKGSRC_LOCKTYPE} == "sleep" || ${PKGSRC_LOCKTYPE} == "once"
Move test for the lockfile within the target's shell code instead of testing for it at the Makefile level.
2006-06-04 07:25:08 +02:00
${_PKG_SILENT}${_PKG_DEBUG} \
Make LOCKFILE into a "private" variable by prepending with an underscore.
2006-06-04 08:09:36 +02:00
${TEST} -f ${_LOCKFILE} || ${RM} -fr ${WRKDIR}
* Turn _SHELL_EXTRACT into a "subroutine" for extracting an archive. It extracts the contents of archive named by the shell variable "extract_file" based on the file extension of the archive. The contents are dumped into the current directory. * Unify the EXTRACT_CMD handling. We now define the default EXTRACT_CMD to be ${_SHELL_EXTRACT} (see above). Otherwise, if it's already defined in the package Makefile, then that EXTRACT_CMD is used to extract all of the archives. * Rearrange the locking code so that it's localized instead of interspersed in the extraction code. * Add EXTRACT_CMD definitions for files that are only compressed (foo.c.gz) that decompress the file into ${WRKDIR}.
2002-02-25 05:43:55 +01:00
. endif
.endif
${_PKG_SILENT}${_PKG_DEBUG}${MKDIR} ${WRKDIR}
Split out the "work" symlink creation into a separate step and add it as a source for the "makedirs" target. This ensures the symlink is created regardless of whether ${WRKDIR} already exists or not.
2006-06-11 04:14:45 +02:00
# Create a symlink from ${WRKDIR} to the package directory if
# CREATE_WRKDIR_SYMLINK is "yes".
#
CREATE_WRKDIR_SYMLINK?= yes
.if defined(WRKOBJDIR) && !empty(CREATE_WRKDIR_SYMLINK:M[Yy][Ee][Ss])
makedirs: ${.CURDIR}/${WRKDIR_BASENAME}
${.CURDIR}/${WRKDIR_BASENAME}:
* Turn _SHELL_EXTRACT into a "subroutine" for extracting an archive. It extracts the contents of archive named by the shell variable "extract_file" based on the file extension of the archive. The contents are dumped into the current directory. * Unify the EXTRACT_CMD handling. We now define the default EXTRACT_CMD to be ${_SHELL_EXTRACT} (see above). Otherwise, if it's already defined in the package Makefile, then that EXTRACT_CMD is used to extract all of the archives. * Rearrange the locking code so that it's localized instead of interspersed in the extraction code. * Add EXTRACT_CMD definitions for files that are only compressed (foo.c.gz) that decompress the file into ${WRKDIR}.
2002-02-25 05:43:55 +01:00
. if ${PKGSRC_LOCKTYPE} == "sleep" || ${PKGSRC_LOCKTYPE} == "once"
${_PKG_SILENT}${_PKG_DEBUG} \
Split out the "work" symlink creation into a separate step and add it as a source for the "makedirs" target. This ensures the symlink is created regardless of whether ${WRKDIR} already exists or not.
2006-06-11 04:14:45 +02:00
${TEST} -f ${_LOCKFILE} || ${RM} -f ${.TARGET}
* Turn _SHELL_EXTRACT into a "subroutine" for extracting an archive. It extracts the contents of archive named by the shell variable "extract_file" based on the file extension of the archive. The contents are dumped into the current directory. * Unify the EXTRACT_CMD handling. We now define the default EXTRACT_CMD to be ${_SHELL_EXTRACT} (see above). Otherwise, if it's already defined in the package Makefile, then that EXTRACT_CMD is used to extract all of the archives. * Rearrange the locking code so that it's localized instead of interspersed in the extraction code. * Add EXTRACT_CMD definitions for files that are only compressed (foo.c.gz) that decompress the file into ${WRKDIR}.
2002-02-25 05:43:55 +01:00
. endif
${_PKG_SILENT}${_PKG_DEBUG} \
Split out the "work" symlink creation into a separate step and add it as a source for the "makedirs" target. This ensures the symlink is created regardless of whether ${WRKDIR} already exists or not.
2006-06-11 04:14:45 +02:00
if ${LN} -s ${WRKDIR} ${.TARGET} 2>/dev/null; then \
${ECHO} "${.TARGET:T} -> ${WRKDIR}"; \
* Turn _SHELL_EXTRACT into a "subroutine" for extracting an archive. It extracts the contents of archive named by the shell variable "extract_file" based on the file extension of the archive. The contents are dumped into the current directory. * Unify the EXTRACT_CMD handling. We now define the default EXTRACT_CMD to be ${_SHELL_EXTRACT} (see above). Otherwise, if it's already defined in the package Makefile, then that EXTRACT_CMD is used to extract all of the archives. * Rearrange the locking code so that it's localized instead of interspersed in the extraction code. * Add EXTRACT_CMD definitions for files that are only compressed (foo.c.gz) that decompress the file into ${WRKDIR}.
2002-02-25 05:43:55 +01:00
fi
Split out the "work" symlink creation into a separate step and add it as a source for the "makedirs" target. This ensures the symlink is created regardless of whether ${WRKDIR} already exists or not.
2006-06-11 04:14:45 +02:00
.endif
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
.include "${PKGSRCDIR}/mk/flavor/bsd.flavor.mk"
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
# Dependencies
.include "${PKGSRCDIR}/mk/depends/bsd.depends.mk"
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
# Check
.include "${PKGSRCDIR}/mk/check/bsd.check.mk"
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
# Clean
.include "../../mk/bsd.pkg.clean.mk"
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
Refactor "fetch" and "extract" code into correspondingly named subdirectories of pkgsrc/mk. Move the following files around for locality: pkgsrc/mk/scripts/extract -> pkgsrc/mk/extract/extract pkgsrc/mk/bsd.sites.mk -> pkgsrc/mk/fetch/sites.mk Also get rid of the recursive make for the "fetch" and "extract" targets. This basically merges the "fetch" and "extract" phases into the "patch" phase. There is still much more work to do to simplify the fetch code, but this is a good start.
2006-06-06 05:05:48 +02:00
# Fetch
.include "${PKGSRCDIR}/mk/fetch/bsd.fetch.mk"
* Add a new stage "bootstrap-depends" that happens before all other stages, and that installs dependencies listed in BOOTSTRAP_DEPENDS. The bootstrap-depends step works just like the normal depends step and honors the value of DEPENDS_TARGET. It's now possible to add dependencies solely to facilitate fetching the distfiles, e.g. BOOTSTRAP_DEPENDS+= curl-[0-9]*:../../www/curl * Teach the tools framework about ":bootstrap" as a tools modifier which indicates the tool should be added as a dependency via BOOTSTRAP_DEPENDS. * Add "digest" to the tools framework. * Use USE_TOOLS+=digest:bootstrap to force pkgsrc to install digest before anything else. Get rid of unused "uptodate-digest" target and related digest version-checking code. * Finish the refactoring work: split checksum-related code out of bsd.pkg.mk and into pkgsrc/mk/checksum and replace the "checksum" target command list with a script that does all the real work. * Make DIGEST_ALGORITHMS and PATCH_DIGEST_ALGORITHM into private variables by prepending them with an underscore. Also, rename _PATCH_DIGEST_ALGORITHM to _PATCH_DIGEST_ALGORITHMS and adjust the makepatchsum target to allow that variable to contain a list of algorithms, all of which are used when creating the patch checksums for ${DISTINFO_FILE}.
2006-07-13 16:02:34 +02:00
# Checksum
.include "${PKGSRCDIR}/mk/checksum/bsd.checksum.mk"
Refactor "fetch" and "extract" code into correspondingly named subdirectories of pkgsrc/mk. Move the following files around for locality: pkgsrc/mk/scripts/extract -> pkgsrc/mk/extract/extract pkgsrc/mk/bsd.sites.mk -> pkgsrc/mk/fetch/sites.mk Also get rid of the recursive make for the "fetch" and "extract" targets. This basically merges the "fetch" and "extract" phases into the "patch" phase. There is still much more work to do to simplify the fetch code, but this is a good start.
2006-06-06 05:05:48 +02:00
# Extract
.include "${PKGSRCDIR}/mk/extract/bsd.extract.mk"
Refactor "patch" code into correspondingly named subdirectory of pkgsrc/mk. Also get rid of the recursive make for the "patch" target. This basically merges the "patch" phase into the "tools" phase. There should eventually be a standalone script that can be used to verify checksums listed in distinfo that should be used instead of the roll-your-own code in the do-pkgsrc-patch target.
2006-06-06 06:48:19 +02:00
# Patch
.include "${PKGSRCDIR}/mk/patch/bsd.patch.mk"
Refactor configure, build, test and wrapper phases out of bsd.pkg.mk and into their own directories. Also do some cleanups with build/_build and pkginstall -- we get rid of _build and simply run pkginstall as part of the "build" target. Introduce a new mechanism to handle varying directory depths under ${WRKSRC} in which we find files to override, e.g. configure, config.*, libtool, etc. OVERRIDE_DIRDEPTH is a package-settable variable that specifies how far under ${WRKSRC} the various targets should look, and it defaults to "2". We preserve the meaning of the various *_OVERRIDE variables, so if they are defined, then their values supersede the OVERRIDE_DIRDEPTH mechanism. devel/tla will need to specially set OVERRIDE_DIRDEPTH to 3 (see log for revision 1.1857 for bsd.pkg.mk -- to be done in a separate commit.
2006-07-05 08:09:15 +02:00
# Configure
.include "${PKGSRCDIR}/mk/configure/bsd.configure.mk"
# Build
.include "${PKGSRCDIR}/mk/build/bsd.build.mk"
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
# Install
.include "${PKGSRCDIR}/mk/install/bsd.install.mk"
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
# Package
.include "${PKGSRCDIR}/mk/package/bsd.package.mk"
* Rename some targets to fit into the usual "do-XXX calls real-XXX" scheme * In real-su-install, do not call "make ${PLIST}" manually, but rather depend on the ${PLIST} file being there for the do-su-install target. * Break out shlib-handlink from real-su-install, and put it into target do-shlib-handling, which will either touch then PLIST (when called via the ${PLIST} target) or do the necessary steps to setup shared library handling (creating symlinks on ELF, running ldconfig on a.out, etc., when called via real-su-install) * Removed some unnecessary tests (check if $PLIST is there when it can be assumed to be there, ...)
2000-11-29 14:18:22 +01:00
Include bsd.pkg.update.mk to get the "update" targets and variables.
2006-06-04 07:26:45 +02:00
.include "${PKGSRCDIR}/mk/bsd.pkg.update.mk"
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
################################################################
# Skeleton targets start here
kill some trailing whitespace
2003-03-30 07:06:49 +02:00
#
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
# You shouldn't have to change these. Either add the pre-* or
# post-* targets/scripts or redefine the do-* targets. These
# targets don't do anything other than checking for cookies and
# call the necessary targets/scripts.
################################################################
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
# su-target is a macro target that does just-in-time su-to-root before
Convert just-in-time su targets to use su-target instead of ${_SU_TARGET}. Garbage-collect the (now) unused _SU_TARGET.
2006-06-04 02:39:05 +02:00
# reinvoking the make process as root. It acquires root privileges and
# invokes a new make process with the target named "su-${.TARGET}".
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
#
Move the common make command executed in su-target into a separate make variable to try to get rid of potential quoting problems.
2006-06-12 18:30:03 +02:00
_ROOT_CMD= cd ${.CURDIR} && \
${SETENV} PATH="$${PATH}:"${SU_CMD_PATH_APPEND:Q} \
${MAKE} ${MAKEFLAGS} \
PKG_DEBUG_LEVEL=${PKG_DEBUG_LEVEL:Q} \
su-${.TARGET} ${MAKEFLAGS.${.TARGET}}
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
.PHONY: su-target
su-target: .USE
Backout previous and fix in another way -- use "set -e" to force the shell to exit if any untested command fails. This is based on Roland Illig's recommendation from his pkglint talk at pkgsrcCon/Paris.
2006-06-05 03:42:58 +02:00
${_PKG_SILENT}${_PKG_DEBUG}set -e; \
Convert just-in-time su targets to use su-target instead of ${_SU_TARGET}. Garbage-collect the (now) unused _SU_TARGET.
2006-06-04 02:39:05 +02:00
case ${PRE_CMD.su-${.TARGET}:Q}"" in \
"") ;; \
*) ${PRE_CMD.su-${.TARGET}} ;; \
esac; \
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
if ${TEST} `${ID} -u` = `${ID} -u ${ROOT_USER}`; then \
Move the common make command executed in su-target into a separate make variable to try to get rid of potential quoting problems.
2006-06-12 18:30:03 +02:00
${_ROOT_CMD}; \
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
else \
case ${PRE_ROOT_CMD:Q}"" in \
${TRUE:Q}"") ;; \
Use PHASE_MSG, STEP_MSG, WARNING_MSG, and ERROR_MSG in place of ECHO_MSG in various places.
2006-06-06 00:49:44 +02:00
*) ${WARNING_MSG} "Running: "${PRE_ROOT_CMD:Q} ;; \
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
esac; \
${PRE_ROOT_CMD}; \
Replaced PHASE_MSG with STEP_MSG in many (but not all) places where it wasn't used to identify a ``phase'', as defined in the pkgsrc guide.
2006-06-08 10:01:53 +02:00
${STEP_MSG} "Becoming \`\`${ROOT_USER}'' to make su-${.TARGET} (`${ECHO} ${SU_CMD} | ${AWK} '{ print $$1 }'`)"; \
Move the common make command executed in su-target into a separate make variable to try to get rid of potential quoting problems.
2006-06-12 18:30:03 +02:00
${SU_CMD} ${_ROOT_CMD:Q}; \
${STEP_MSG} "Dropping \`\`${ROOT_USER}'' privileges."; \
First pass at implementing support for package system flavors other 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-06-04 01:11:42 +02:00
fi
Add two new EXPERIMENTAL targets: replace - this target updates a package in place, fixing up references to and from other packages to the updated package. undo-replace - undoes all the work of the previous replace operation. For this target to work, the ${WRKDIR} must be preserved. The replace target first makes a binary package of the existing installed package, then a copy of the +REQUIRED_BY file is taken, if it exists, and then the existing package is deleted. The new package is installed, and the preserved +REQUIRED_BY file is copied back into place, using its contents to modify the +CONTENTS files of all the packages which require it. The undo-replace shares code with the replace target, and does the same operation, but in reverse. Warnings are displayed when either of these targets is used, since they are experimental targets right now.
2002-03-04 12:56:54 +01:00
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
################################################################
# Some more targets supplied for users' convenience
################################################################
* Remove old PLIST-mi/md.shared/md.static that was only used for perl in a previous (pkgsrc) life. * add "lint" target to run pkglint * Add commented out direction on how to use bzip2 compressed binary packages * Some cleanup (clean target, ...) Reviewed by Thomas Klauser <wiz@netbsd.org>.
2000-12-30 12:19:04 +01:00
# Run pkglint:
Mark all targets that do not correspond to real files with the .PHONY attribute.
2003-07-24 00:02:48 +02:00
.PHONY: lint
* Remove old PLIST-mi/md.shared/md.static that was only used for perl in a previous (pkgsrc) life. * add "lint" target to run pkglint * Add commented out direction on how to use bzip2 compressed binary packages * Some cleanup (clean target, ...) Reviewed by Thomas Klauser <wiz@netbsd.org>.
2000-12-30 12:19:04 +01:00
lint:
pkglint does not output any "OK" lines by default, so there's no need to filter them out.
2005-06-27 18:25:43 +02:00
${_PKG_SILENT}${_PKG_DEBUG}${LOCALBASE}/bin/pkglint
Add new "tarup" target which allows to create a binary package from an installed package with the "pkg_tarup" utility.
2001-07-10 13:51:57 +02:00
make the bin-install target look at some FTP servers (stored in BINPKG_SITES). As discussed on tech-pkg.
2001-05-20 03:58:19 +02:00
# List of sites carrying binary pkgs. Variables "rel" and "arch" are
# replaced with OS release ("1.5", ...) and architecture ("mipsel", ...)
rename BINPKG_SITE to BINPKG_SITES Adresses PR pkg/19004 by tv@pobox.com
2002-11-10 19:20:44 +01:00
BINPKG_SITES?= \
s/netbsd.org/NetBSD.org/, s/freebsd.org/FreeBSD.org/
2004-02-25 10:24:52 +01:00
ftp://ftp.NetBSD.org/pub/NetBSD/packages/$${rel}/$${arch}
make the bin-install target look at some FTP servers (stored in BINPKG_SITES). As discussed on tech-pkg.
2001-05-20 03:58:19 +02:00
Merge pkgviews-mk branch into the HEAD by running: cd pkgsrc/mk cvs update -Pd -A cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
2003-09-02 08:59:37 +02:00
# List of flags to pass to pkg_add(1) for bin-install:
make the bin-install target look at some FTP servers (stored in BINPKG_SITES). As discussed on tech-pkg.
2001-05-20 03:58:19 +02:00
BIN_INSTALL_FLAGS?= # -v
Merge pkgviews-mk branch into the HEAD by running: cd pkgsrc/mk cvs update -Pd -A cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
2003-09-02 08:59:37 +02:00
.if ${PKG_INSTALLATION_TYPE} == "pkgviews"
We want to add consistently add to the default view if we use pkgviews and pkg_add'ing.
2003-09-08 03:06:01 +02:00
PKG_ARGS_ADD= -W ${LOCALBASE} -w ${DEFAULT_VIEW}
Merge pkgviews-mk branch into the HEAD by running: cd pkgsrc/mk cvs update -Pd -A cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
2003-09-02 08:59:37 +02:00
.endif
_BIN_INSTALL_FLAGS= ${BIN_INSTALL_FLAGS}
Handle automatic dependencies in bin-install correctly. From Chapman Flack in PR 32422.
2005-12-31 08:53:11 +01:00
.if defined(_AUTOMATIC) && !empty(_AUTOMATIC:MYES)
_BIN_INSTALL_FLAGS+= -A
Use new automatic flag; depend on appropriate pkg_install version.
2005-11-05 14:31:43 +01:00
.endif
Merge pkgviews-mk branch into the HEAD by running: cd pkgsrc/mk cvs update -Pd -A cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
2003-09-02 08:59:37 +02:00
_BIN_INSTALL_FLAGS+= ${PKG_ARGS_ADD}
make the bin-install target look at some FTP servers (stored in BINPKG_SITES). As discussed on tech-pkg.
2001-05-20 03:58:19 +02:00
In the bin-install target, instead of running pkg_add for every BINPKG_SITES entry separately, construct an appropriate PKG_PATH and call pkg_add only once. Patch from Chapman Flack in PR 30929. Use PKGNAME_REQD when installing package dependencies. Patch from Chapman Flack in PR 30954.
2006-01-03 18:26:56 +01:00
_SHORT_UNAME_R= ${:!${UNAME} -r!:C@\.([0-9]*)[_.].*@.\1@} # n.n[_.]anything => n.n
Add bin-install package: will install a binary package if available, else run a "make package". XXX needs to be extended to also look on some FTP sites.
2000-07-06 18:45:21 +02:00
# Install binary pkg, without strict uptodate-check first
Convert just-in-time su targets to use su-target instead of ${_SU_TARGET}. Garbage-collect the (now) unused _SU_TARGET.
2006-06-04 02:39:05 +02:00
.PHONY: su-bin-install
su-bin-install:
In cases where we need the best match for a pkgpattern, use "${PKG_BEST_EXIST} pkgpattern" instead of "${PKG_INFO} -e pkgpattern". The latter can return multiple package names if there are multiple versions of a piece of software installed. PKG_BEST_EXIST is defined to be "${PKG_ADMIN} -b -d ${_PKG_DBDIR} -s "" lsbest", so it searches for the best installed package that matches the given pkgpattern or else returns the empty string. Bump PKGTOOLS_REQD to 20030912 since pkg_admin(1) needs to know about "-b" and "-d <dir>".
2003-09-13 07:55:14 +02:00
@found="`${PKG_BEST_EXISTS} \"${PKGWILDCARD}\" || ${TRUE}`"; \
make the bin-install target look at some FTP servers (stored in BINPKG_SITES). As discussed on tech-pkg.
2001-05-20 03:58:19 +02:00
if [ "$$found" != "" ]; then \
Use PHASE_MSG, STEP_MSG, WARNING_MSG, and ERROR_MSG in place of ECHO_MSG in various places.
2006-06-06 00:49:44 +02:00
${ERROR_MSG} "$$found is already installed - perhaps an older version?"; \
${ERROR_MSG} "If so, you may wish to \`\`pkg_delete $$found'' and install"; \
${ERROR_MSG} "this package again by \`\`${MAKE} bin-install'' to upgrade it properly."; \
make the bin-install target look at some FTP servers (stored in BINPKG_SITES). As discussed on tech-pkg.
2001-05-20 03:58:19 +02:00
exit 1; \
fi
In the bin-install target, instead of running pkg_add for every BINPKG_SITES entry separately, construct an appropriate PKG_PATH and call pkg_add only once. Patch from Chapman Flack in PR 30929. Use PKGNAME_REQD when installing package dependencies. Patch from Chapman Flack in PR 30954.
2006-01-03 18:26:56 +01:00
@rel=${_SHORT_UNAME_R:Q} ; \
arch=${MACHINE_ARCH:Q} ; \
pkgpath=${PKGREPOSITORY:Q} ; \
for i in ${BINPKG_SITES} ; do pkgpath="$$pkgpath;$$i/All" ; done ; \
${ECHO} "Trying $$pkgpath" ; \
if ${SETENV} PKG_PATH="$$pkgpath" ${PKG_ADD} ${_BIN_INSTALL_FLAGS} ${PKGNAME_REQD:U${PKGNAME}:Q}${PKG_SUFX} ; then \
${ECHO} "`${PKG_INFO} -e ${PKGNAME_REQD:U${PKGNAME}:Q}` successfully installed."; \
else \
${SHCOMMENT} Cycle through some FTP server here ;\
${ECHO_MSG} "Installing from source" ; \
${MAKE} ${MAKEFLAGS} package \
DEPENDS_TARGET=${DEPENDS_TARGET:Q} && \
${MAKE} ${MAKEFLAGS} clean ; \
Add bin-install package: will install a binary package if available, else run a "make package". XXX needs to be extended to also look on some FTP sites.
2000-07-06 18:45:21 +02:00
fi
Fix PR 17883 by adding code to perform just-in-time su(1) functionality for the bin-install target.
2003-10-18 14:29:26 +02:00
.PHONY: bin-install
Convert just-in-time su targets to use su-target instead of ${_SU_TARGET}. Garbage-collect the (now) unused _SU_TARGET.
2006-06-04 02:39:05 +02:00
bin-install: su-target
Use PHASE_MSG, STEP_MSG, WARNING_MSG, and ERROR_MSG in place of ECHO_MSG in various places.
2006-06-06 00:49:44 +02:00
@${PHASE_MSG} "Binary install for "${PKGNAME_REQD:U${PKGNAME}:Q}
Fix PR 17883 by adding code to perform just-in-time su(1) functionality for the bin-install target.
2003-10-18 14:29:26 +02:00
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
################################################################
# Everything after here are internal targets and really
# shouldn't be touched by anybody but the release engineers.
################################################################
Mark all targets that do not correspond to real files with the .PHONY attribute.
2003-07-24 00:02:48 +02:00
.PHONY: show-pkgtools-version
Add Solaris support to pkgsrc, using Christos Zoulas' NetBSD emulation package. Tested for some packages on Solaris 2.6 on Sparc.
1999-03-08 18:26:54 +01:00
.if !target(show-pkgtools-version)
show-pkgtools-version:
Calculate current pkgtools version once (inline rather than via additional make call), and pass it in the environment to any recursive make calls. 'make fetch' in gnumeric on my system is now > 15% faster checking dependencies.
2000-01-07 13:24:14 +01:00
@${ECHO} ${PKGTOOLS_VERSION}
if ${IDENT} does not exist, assume that the package tools are ok. This is for bootstrapping on systems that don't have RCS installed.
1999-08-31 23:45:45 +02:00
.endif
add print-pkgtools_ver to get version of currently-installed pkg-tools
1998-11-09 15:41:30 +01:00
Add a convenience target called "show-var", which will echo a make(1) variable from the command line: i.e. "make show-var VARNAME=var" will echo var's value
1999-09-28 12:03:16 +02:00
# convenience target, to display make variables from command line
# i.e. "make show-var VARNAME=var", will print var's value
Mark all targets that do not correspond to real files with the .PHONY attribute.
2003-07-24 00:02:48 +02:00
.PHONY: show-var
Add a convenience target called "show-var", which will echo a make(1) variable from the command line: i.e. "make show-var VARNAME=var" will echo var's value
1999-09-28 12:03:16 +02:00
show-var:
show-var: implement quoting via make's :Q modifier, instead of home-brewn.
2001-04-17 18:56:21 +02:00
@${ECHO} ${${VARNAME}:Q}
Add a convenience target called "show-var", which will echo a make(1) variable from the command line: i.e. "make show-var VARNAME=var" will echo var's value
1999-09-28 12:03:16 +02:00
Add a new "show-vars" target which allows to display several makefile variables at once.
2001-10-26 23:42:44 +02:00
# enhanced version of target above, to display multiple variables
Mark all targets that do not correspond to real files with the .PHONY attribute.
2003-07-24 00:02:48 +02:00
.PHONY: show-vars
Add a new "show-vars" target which allows to display several makefile variables at once.
2001-10-26 23:42:44 +02:00
show-vars:
.for VARNAME in ${VARNAMES}
@${ECHO} ${${VARNAME}:Q}
.endfor
Add "show-vars-eval" target, which outputs eval-able shell expressions to allow easy setting of multiple variables in one invocation.
2005-10-16 19:44:45 +02:00
# displays multiple variables as shell expressions
# VARS is space separated list of VARNAME:shellvarname
.PHONY: show-vars-eval
show-vars-eval:
.for var in ${VARS}
@${ECHO} ${var:C/^.*://}="${${var:C/:.*$//}:Q}"
.endfor
Added a variable LICENSE_FILE that may be set to point to the license file of the package. It does _not_ replace the LICENSE variable. The variable is currently only used in the show-license target. It is intended that LICENSE_FILE is used for licenses that only apply to a single package or a package group, so that the number of licenses in the licenses/ directory is kept small.
2005-09-28 10:24:52 +02:00
LICENSE_FILE?= ${PKGSRCDIR}/licenses/${LICENSE}
Add a "show-license" target, and a "show-licence" alias, to display the package's licence, if it's non-standard.
2001-01-05 18:37:12 +01:00
.if !target(show-license)
show-license show-licence:
Added a variable LICENSE_FILE that may be set to point to the license file of the package. It does _not_ replace the LICENSE variable. The variable is currently only used in the show-license target. It is intended that LICENSE_FILE is used for licenses that only apply to a single package or a package group, so that the number of licenses in the licenses/ directory is kept small.
2005-09-28 10:24:52 +02:00
@license=${LICENSE:Q}; \
license_file=${LICENSE_FILE:Q}; \
pager=${PAGER:Q}; \
case "$$pager" in "") pager=${CAT:Q};; esac; \
case "$$license" in "") exit 0;; esac; \
if ${TEST} -f "$$license_file"; then \
$$pager "$$license_file"; \
else \
${ECHO} "Generic $$license information not available"; \
${ECHO} "See the package description (pkg_info -d ${PKGNAME}) for more information."; \
Add a "show-license" target, and a "show-licence" alias, to display the package's licence, if it's non-standard.
2001-01-05 18:37:12 +01:00
fi
.endif
Add code to include the size of a package into both the installed version and binary packages. The size can be queried then via pkg_info: xfeyrer @ noon% pkg_info -s xv Information for xv-3.10apl1: Size of this package in bytes: 4670692 xfeyrer @ noon% pkg_info -S xv Information for xv-3.10apl1: Size in bytes including required pkgs: 14610165 While doing work on the size code, support for the @src directive was removed (formerly enabled with the pkg_create -s switch, but unused in our pkg system). The new pkg_info -s and -S switches were tested on installed, local (file) and remote (ftp) packages. In bsd.pkg.mk, take special care for pkg_* versions that do not have the pkg_create -s and -S switches and do not record size information there.
1999-11-29 20:48:15 +01:00
Add a dummy describe-options target for package not using the options framework.
2005-05-08 15:52:25 +02:00
# This target is defined in bsd.options.mk for packages that use
# the options framework.
Rename describe-options to show-options, replacing the old show-options target.
2005-05-31 14:10:07 +02:00
.if !target(show-options)
.PHONY: show-options
show-options:
Add a dummy describe-options target for package not using the options framework.
2005-05-08 15:52:25 +02:00
@${ECHO} This package does not use the options framework.
.endif
This is NetBSD. s/port/package/g
1999-08-10 12:48:23 +02:00
# Depend is generally meaningless for arbitrary packages, but if someone wants
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
# one they can override this. This is just to catch people who've gotten into
make -> ${MAKE}, as per FreeBSD's PR 6341.
1998-04-19 14:48:07 +02:00
# the habit of typing `${MAKE} depend all install' as a matter of course.
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
#
Mark all targets that do not correspond to real files with the .PHONY attribute.
2003-07-24 00:02:48 +02:00
.PHONY: depend
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
.if !target(depend)
depend:
.endif
# Same goes for tags
Mark all targets that do not correspond to real files with the .PHONY attribute.
2003-07-24 00:02:48 +02:00
.PHONY: tags
Initial import of FreeBSD's ports makefiles.
1997-08-20 12:21:05 +02:00
.if !target(tags)
tags:
.endif
- Add OpenBSD and FreeBSD Ids in the header - Changes from FreeBSD's V1.164: * Warn if mtree-file not found * On 'make reinstall' gets DEPENDS_TARGET set to 'reinstall' instead of 'install' - Changes from OpenBSD's V1.14: * Documentation and implementation for ONLY_FOR_ARCHS * Documentation and implementation for WRKOBJDIR * Documentation on HAVE_MOTIF and MOTIF_STATIC: set in /etc/mk.conf, not /etc/make.conf * Set NOMANCOMPRESS=no to still compress man-pages (should probably be set to 'yes') * DEF_UMASK=022 * add ${MACHINE} suffix to WRKDIR if OBJMACHINE is set * .include <bsd.own.mk>
1997-09-28 02:44:15 +02:00
Initial commit of a new module that encapsulates all of the code for manipulating PLISTs. This module is not used by default pending more widespread testing -- currently the variable _USE_PLIST_MODULE must be defined in /etc/mk.conf to enable its use. The main features of the new PLIST module are: (1) Splits out the PLIST-handling code from bsd.pkg.mk into a separate "plist" module. (2) Splits out giant, multi-line awk scripts stored in make variables into separate awk scripts that may be joined together to post-process PLISTs. Each of these awk scripts consolidates the processing for one set of files, e.g., man pages, info pages, etc., and is more easily commented than a make variable. (3) Splits out the print-PLIST code from the regular PLIST code since they have no common pieces (print-plist.mk vs. plist.mk). (4) Completely re-implements the shared-library handling to be more efficient. Along the way, this also fixes a problem for Mac OS X users where the PLISTs incorrectly contained absolute paths. (5) Completely re-implements the info-file handling so that we can migrate from INFO_FILES definitions to just adding info/foo.info entries in the static PLISTs. (6) Adds commented-out support for automatically compressed or decompressed info page entries based on the value of MANZ. These changes will be activated after texinfo.mk has been replaced by something that is built using the more modern primitives now available in pkgsrc. (7) Move the file compression logic into a separate script "doc-compress" that compresses or decompresses files while minding symlinks. This script is now called by bsd.pkg.mk to do the "autmoatic man page handling". In the future, it will also handle the "automatic info page handling" and possible others. In general, the idea is to move stuff out of the Makefiles and into separate files where we don't need to worry about quoting rules and where each file can have a separate history of commits. This simplifies the makefile logic (especially in terms of readability) and also simplifies maintenance of the code.
2006-01-13 00:43:56 +01:00
.include "../../mk/plist/bsd.plist.mk"
Create a standalone awk script, depends-depth-first.awk, that encapsulates the code that performs the dependency graph traversal (in depth-first fashion). This script has a hook that allows executing a shell command line upon visiting a dependency's package directory in either prefix or postfix order, and may be used to simplify the code in bsd.pkg.mk that iterates over dependencies. This awk script requires the target "show-depends-pkgpaths", which is defined in a new Makefile pkgsrc/mk/bsd.utils.mk. This file should accumulate "utility" targets that current exist in bsd.pkg.mk, i.e., "helper" targets for various actions.
2006-01-18 01:10:07 +01:00
.include "../../mk/bsd.utils.mk"
(*) Nuke the _BUILDLINK_SUBST_USE target now that subst.mk does the same thing. (*) Move the code to adjust Makefiles to refer to the correct PKGLOCALEDIR into bsd.pkg.mk and reimplement it using subst.mk so that it's non-USE_BUILDLINK2 packages can use it, too. (*) Reimplement the PKGCONFIG_OVERRIDE code in bsd.pkg.mk using subst.mk. (*) Reimplement the unbuildlink code in bsd.buildlink2.mk using subst.mk.
2003-08-27 13:29:56 +02:00
.include "../../mk/subst.mk"
Pull in bulk-build targets if BATCH is set
2000-07-28 03:16:27 +02:00
#
# For bulk build targets (bulk-install, bulk-package), the
* Remove RUN_DEPENDS (left in packages.7 intentionally) * Renamed misc-depends to run-depends, and drop (old) run-depends altogether Code reviewed by wiz.
2000-08-01 04:16:58 +02:00
# BATCH variable must be set in /etc/mk.conf:
Pull in bulk-build targets if BATCH is set
2000-07-28 03:16:27 +02:00
#
.if defined(BATCH)
Change indentation (whitespace changes only!): .if .if .if . if .else => . else .endif . endif .endif .endif Patch contributed by Marc Espie <espie@liafa.jussieu.fr> in preparation of merging latest changes with the OpenPackages project. Thanks Marc!
2001-07-19 00:43:32 +02:00
. include "../../mk/bulk/bsd.bulk-pkg.mk"
Pull in bulk-build targets if BATCH is set
2000-07-28 03:16:27 +02:00
.endif
Allow the creation of error handlers for shell commands in make targets. PKG_ERROR_CLASSES is a list of error handlers, PKG_ERROR_HANDLER.<class>, to create. The default error handler will rethrow the exit code after emitting an error message that may be specified per-class with PKG_ERROR_MSG.<class>. Create error messages for the configure and build phases that inform the user of places to go looking for why the build didn't complete.
2005-01-10 19:34:48 +01:00
Refactor the README.html generation code from bsd.pkg.mk into a separate bsd.pkg.readme.mk and document the public targets and variables for this new file.
2006-07-06 23:07:33 +02:00
# README generation code.
.include "../../mk/bsd.pkg.readme.mk"
Allow the creation of error handlers for shell commands in make targets. PKG_ERROR_CLASSES is a list of error handlers, PKG_ERROR_HANDLER.<class>, to create. The default error handler will rethrow the exit code after emitting an error message that may be specified per-class with PKG_ERROR_MSG.<class>. Create error messages for the configure and build phases that inform the user of places to go looking for why the build didn't complete.
2005-01-10 19:34:48 +01:00
# Create a PKG_ERROR_HANDLER shell command for each class listed in
# PKG_ERROR_CLASSES. The error handler is meant to be invoked within
# a make target.
#
.for _class_ in ${PKG_ERROR_CLASSES}
PKG_ERROR_HANDLER.${_class_}?= { \
ec=$$?; \
for str in ${PKG_ERROR_MSG.${_class_}}; do \
Use PHASE_MSG, STEP_MSG, WARNING_MSG, and ERROR_MSG in place of ECHO_MSG in various places.
2006-06-06 00:49:44 +02:00
${PHASE_MSG} "$$str"; \
Allow the creation of error handlers for shell commands in make targets. PKG_ERROR_CLASSES is a list of error handlers, PKG_ERROR_HANDLER.<class>, to create. The default error handler will rethrow the exit code after emitting an error message that may be specified per-class with PKG_ERROR_MSG.<class>. Create error messages for the configure and build phases that inform the user of places to go looking for why the build didn't complete.
2005-01-10 19:34:48 +01:00
done; \
exit $$ec; \
}
.endfor
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
Rename MAKE_VARS to MAKEVARS so that it more closely resembles "MAKEFLAGS". Both "MAKEVARS" and "MAKEFLAGS" affect the package-level make process, not the software's own make process.
2005-05-12 00:08:18 +02:00
# Cache variables listed in MAKEVARS in a phase-specific "makevars.mk"
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
# file. These variables are effectively passed to sub-make processes
# that are invoked on the same Makefile.
#
Completely nuke the concept of PKG_PHASE from pkgsrc except for the purposes of caching MAKEVARS within bsd.pkg.mk and bsd.makevars.mk.
2006-07-11 00:59:26 +02:00
.for _phase_ in ${_ALL_PHASES}
Rename MAKE_VARS to MAKEVARS so that it more closely resembles "MAKEFLAGS". Both "MAKEVARS" and "MAKEFLAGS" affect the package-level make process, not the software's own make process.
2005-05-12 00:08:18 +02:00
${_MAKEVARS_MK.${_phase_}}: ${WRKDIR}
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
${_PKG_SILENT}${_PKG_DEBUG}${RM} -f ${.TARGET}.tmp
Refactor "fetch" and "extract" code into correspondingly named subdirectories of pkgsrc/mk. Move the following files around for locality: pkgsrc/mk/scripts/extract -> pkgsrc/mk/extract/extract pkgsrc/mk/bsd.sites.mk -> pkgsrc/mk/fetch/sites.mk Also get rid of the recursive make for the "fetch" and "extract" targets. This basically merges the "fetch" and "extract" phases into the "patch" phase. There is still much more work to do to simplify the fetch code, but this is a good start.
2006-06-06 05:05:48 +02:00
. for _var_ in ${MAKEVARS:O:u}
. if defined(${_var_})
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
${_PKG_SILENT}${_PKG_DEBUG} \
${ECHO} ${_var_}"= "${${_var_}:Q} >> ${.TARGET}.tmp
Refactor "fetch" and "extract" code into correspondingly named subdirectories of pkgsrc/mk. Move the following files around for locality: pkgsrc/mk/scripts/extract -> pkgsrc/mk/extract/extract pkgsrc/mk/bsd.sites.mk -> pkgsrc/mk/fetch/sites.mk Also get rid of the recursive make for the "fetch" and "extract" targets. This basically merges the "fetch" and "extract" phases into the "patch" phase. There is still much more work to do to simplify the fetch code, but this is a good start.
2006-06-06 05:05:48 +02:00
. endif
. endfor
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
${_PKG_SILENT}${_PKG_DEBUG} \
if ${TEST} -f ${.TARGET}.tmp; then \
Rename MAKE_VARS to MAKEVARS so that it more closely resembles "MAKEFLAGS". Both "MAKEVARS" and "MAKEFLAGS" affect the package-level make process, not the software's own make process.
2005-05-12 00:08:18 +02:00
( ${ECHO} ".if !defined(_MAKEVARS_MK)"; \
${ECHO} "_MAKEVARS_MK= defined"; \
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
${ECHO} ""; \
${CAT} ${.TARGET}.tmp; \
${ECHO} ""; \
Rename MAKE_VARS to MAKEVARS so that it more closely resembles "MAKEFLAGS". Both "MAKEVARS" and "MAKEFLAGS" affect the package-level make process, not the software's own make process.
2005-05-12 00:08:18 +02:00
${ECHO} ".endif # _MAKEVARS_MK"; \
Teach bsd.pkg.mk to create a phase-specific "makevars.mk" file that caches variable definitions that were computed by make. These variables are specified by listing them in MAKE_VARS, e.g., .if !defined(FOO) FOO!= very_time_consuming_command .endif MAKE_VARS+= FOO bsd.pkg.mk will include only the one generated during the most recent phase. A particular phase's makevars.mk file consists of variable definitions that are a superset of all of the ones produced in previous phases of the build. The caching is useful because bsd.pkg.mk invokes make recursively, which in the example above has the potential to run the very time-consuming command each time unless we cause FOO to be defined for the sub-make processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't consistently applied to every invocation of make, and also because MAKE_FLAGS can overflow the maximum length of a make variable very quickly if we add many values to it. One important and desirable property of variables cached via MAKE_VARS is that they only apply to the current package, and not to any dependencies whose builds may have been triggered by the current package. The makevars.mk files are generated by new targets fetch-vars, extract-vars, patch-vars, etc., and these targets are built during the corresponding real-* target to ensure that they are being invoked with PKG_PHASE set to the proper value. Also, remove the variables cache file that bsd.wrapper.mk was generating since the new makevars.mk files provide the same functionality at a higher level. Change all WRAPPER_VARS definitions that were used by the old wrapper-phase cache file into MAKE_VARS definitions.
2005-05-09 07:06:55 +02:00
) > ${.TARGET}; \
${RM} -f ${.TARGET}.tmp; \
fi
${_PKG_SILENT}${_PKG_DEBUG}${TOUCH} ${TOUCH_FLAGS} ${.TARGET}
.endfor
Added the show-tools target, which emits a shell code fragment defining all tools known to the pkgsrc infrastructure.
2005-05-18 04:52:38 +02:00
# show-tools emits a /bin/sh shell script that defines all known tools
# to the values they have in the pkgsrc infrastructure.
#
# Don't move this code away from here unless you know what you're doing.
#
.PHONY: show-tools
show-tools:
.for _t_ in ${_USE_TOOLS}
. if defined(_TOOLS_VARNAME.${_t_})
Fixed the output of show-tools.
2005-05-26 13:15:30 +02:00
@${ECHO} ${_TOOLS_VARNAME.${_t_}:Q}=${${_TOOLS_VARNAME.${_t_}}:Q:Q}
Added the show-tools target, which emits a shell code fragment defining all tools known to the pkgsrc infrastructure.
2005-05-18 04:52:38 +02:00
. endif
.endfor
Add changes-entry target, which adds an entry for the current package into pkgsrc/doc/CHANGES. The type of the entry depends on what CTYPE is set to, which defaults to "Updated". Other possible values are "Added", "Renamed", "Moved", and "Removed". An example usage would be: cd /usr/pkgsrc/category/package make changes-entry CTYPE=Added after you added a new package, and similar for the others. If NETBSD_LOGIN_NAME is not set in /etc/mk.conf, it defaults to your local login name.
2005-06-09 00:44:08 +02:00
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
# changes-entry appends a correctly-formatted entry to the pkgsrc
# CHANGES file.
Add a documentation block above the changes-entry target.
2005-06-09 18:08:27 +02:00
#
# The following variables may be set:
#
# CTYPE is the type of entry to add and is one of "Added", "Updated",
# "Renamed", "Moved", of "Removed". The default CTYPE is "Updated".
#
# NETBSD_LOGIN_NAME is the login name assigned by the NetBSD Project.
# It defaults to the local login name.
#
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
# PKGSRC_CHANGES is the path to the CHANGES file to which the entry
# is appended. It defaults to ${PKGSRCDIR}/doc/CHANGES.
#
Add a documentation block above the changes-entry target.
2005-06-09 18:08:27 +02:00
# Example usage:
#
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
# % cd /usr/pkgsrc/category/package
# % make changes-entry CTYPE=Added
Add a documentation block above the changes-entry target.
2005-06-09 18:08:27 +02:00
#
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
CTYPE?= Updated
NETBSD_LOGIN_NAME?= ${_NETBSD_LOGIN_NAME_cmd:sh}
Rename the CHANGES file to CHANGES-2006. From now on, the changes for each year will accumulate in CHANGES-YYYY.
2006-04-18 02:25:04 +02:00
PKGSRC_CHANGES?= ${PKGSRCDIR}/doc/CHANGES-${_CYEAR_cmd:sh}
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
Rename the CHANGES file to CHANGES-2006. From now on, the changes for each year will accumulate in CHANGES-YYYY.
2006-04-18 02:25:04 +02:00
_CYEAR_cmd= ${DATE} -u +%Y
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
_CDATE_cmd= ${DATE} -u +%Y-%m-%d
_NETBSD_LOGIN_NAME_cmd= ${ID} -nu
_CTYPE1= " "${CTYPE:Q}" "${PKGPATH:Q}
Add changes-entry target, which adds an entry for the current package into pkgsrc/doc/CHANGES. The type of the entry depends on what CTYPE is set to, which defaults to "Updated". Other possible values are "Added", "Renamed", "Moved", and "Removed". An example usage would be: cd /usr/pkgsrc/category/package make changes-entry CTYPE=Added after you added a new package, and similar for the others. If NETBSD_LOGIN_NAME is not set in /etc/mk.conf, it defaults to your local login name.
2005-06-09 00:44:08 +02:00
.if !empty(CTYPE:MUpdated)
_CTYPE2= " to "${PKGVERSION:Q}
.elif !empty(CTYPE:MAdded)
_CTYPE2= " version "${PKGVERSION:Q}
.elif !empty(CTYPE:MRenamed) || !empty(CTYPE:MMoved)
_CTYPE2= " to XXX"
.else
_CTYPE2=
.endif
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
_CTYPE3= " ["${NETBSD_LOGIN_NAME:Q}" "${_CDATE_cmd:sh:Q}"]"
Add changes-entry target, which adds an entry for the current package into pkgsrc/doc/CHANGES. The type of the entry depends on what CTYPE is set to, which defaults to "Updated". Other possible values are "Added", "Renamed", "Moved", and "Removed". An example usage would be: cd /usr/pkgsrc/category/package make changes-entry CTYPE=Added after you added a new package, and similar for the others. If NETBSD_LOGIN_NAME is not set in /etc/mk.conf, it defaults to your local login name.
2005-06-09 00:44:08 +02:00
.PHONY: changes-entry
changes-entry:
General improvements to the changes-entry target: * Improve the documentation. * Avoid running commands during Makefile processing by using the :sh modifier instead of defining variables using != * Add a new variable PKGSRC_CHANGES that holds the path to the CHANGES file to be modified. * Use ${ID} and ${DATE}, which are provided by the tools framework and avoid PATH issues.
2005-06-09 18:26:23 +02:00
${_PKG_SILENT}${_PKG_DEBUG} \
${ECHO} ${_CTYPE1}${_CTYPE2}${_CTYPE3} >> ${PKGSRC_CHANGES:Q}
Reference in a new issue Copy permalink