Makefile revision 9f9230833b50b8271840dc2c12bd1e94d9df7d12
3b4098640dd85040270f39b9a5ee5e22de99d3d6Mark Andrews# CDDL HEADER START
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The contents of this file are subject to the terms of the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Common Development and Distribution License (the "License").
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# You may not use this file except in compliance with the License.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# See the License for the specific language governing permissions
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# and limitations under the License.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# When distributing Covered Code, include this CDDL HEADER in each
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# If applicable, add the following below this CDDL HEADER, with the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# fields enclosed by brackets "[]" replaced with your own identifying
dca44b90c96352111e0f1cdfdeccde1a13732161Mark Andrews# information: Portions Copyright [yyyy] [name of copyright owner]
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# CDDL HEADER END
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Copyright 2015, OmniTI Computer Consulting, Inc. All rights reserved.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Copyright 2015 Igor Kozhukhov <ikozhukhov@gmail.com>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Make sure we're getting a consistent execution environment for the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# embedded scripts.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# To suppress package dependency generation on any system, regardless
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# of how it was installed, set SUPPRESSPKGDEP=true in the build
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# environment.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Comment this line out or set "PKGDEBUG=" in your build environment
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# to get more verbose output from the make processes in usr/src/pkg
3b4098640dd85040270f39b9a5ee5e22de99d3d6Mark Andrews# Cross platform packaging notes
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# By default, we package the proto area from the same architecture as
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# the packaging build. In other words, if you're running nightly or
3b4098640dd85040270f39b9a5ee5e22de99d3d6Mark Andrews# bldenv on an x86 platform, it will take objects from the x86 proto
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# area and use them to create x86 repositories.
3b4098640dd85040270f39b9a5ee5e22de99d3d6Mark Andrews# If you want to create repositories for an architecture that's
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# different from $(uname -p), you do so by setting PKGMACH in your
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# build environment.
3b4098640dd85040270f39b9a5ee5e22de99d3d6Mark Andrews# For this to work correctly, the following must all happen:
3b4098640dd85040270f39b9a5ee5e22de99d3d6Mark Andrews# 1. You need the desired proto area, which you can get either by
3b4098640dd85040270f39b9a5ee5e22de99d3d6Mark Andrews# doing a gatekeeper-style build with the -U option to
7329012471d165cd3dc4180ad2a0a43de91e7f01Mark Andrews# nightly(1), or by using rsync. If you don't do this, you will
7329012471d165cd3dc4180ad2a0a43de91e7f01Mark Andrews# get packaging failures building all packages, because pkgsend
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# is unable to find the required binaries.
7329012471d165cd3dc4180ad2a0a43de91e7f01Mark Andrews# 2. You need the desired tools proto area, which you can get in the
7329012471d165cd3dc4180ad2a0a43de91e7f01Mark Andrews# same ways as the normal proto area. If you don't do this, you
7329012471d165cd3dc4180ad2a0a43de91e7f01Mark Andrews# will get packaging failures building onbld, because pkgsend is
7329012471d165cd3dc4180ad2a0a43de91e7f01Mark Andrews# unable to find the tools binaries.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# 3. The remainder of this Makefile should never refer directly to
7329012471d165cd3dc4180ad2a0a43de91e7f01Mark Andrews# $(MACH). Instead, $(PKGMACH) should be used whenever an
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# architecture-specific path or token is needed. If this is done
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# incorrectly, then packaging will fail, and you will see the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# value of $(uname -p) instead of the value of $(PKGMACH) in the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# commands that fail.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# 4. Each time a rule in this Makefile invokes $(MAKE), it should
dca44b90c96352111e0f1cdfdeccde1a13732161Mark Andrews# pass PKGMACH=$(PKGMACH) explicitly on the command line. If
dca44b90c96352111e0f1cdfdeccde1a13732161Mark Andrews# this is done incorrectly, then packaging will fail, and you
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# will see the value of $(uname -p) instead of the value of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# $(PKGMACH) in the commands that fail.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Refer also to the convenience targets defined later in this
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# ROOT, TOOLS_PROTO, and PKGARCHIVE should be set by nightly or
dca44b90c96352111e0f1cdfdeccde1a13732161Mark Andrews# bldenv. These macros translate them into terms of $PKGMACH, instead
dca44b90c96352111e0f1cdfdeccde1a13732161Mark AndrewsPKGROOT.cmd= print $(ROOT) | sed -e s:/root_$(MACH):/root_$(PKGMACH):
7208386cd37a2092c70eddf80cf29519b16c4c80Mark AndrewsTOOLSROOT.cmd= print $(TOOLS_PROTO) | sed -e s:/root_$(MACH):/root_$(PKGMACH):
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinPKGDEST.cmd= print $(PKGARCHIVE) | sed -e s:/$(MACH)/:/$(PKGMACH)/:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Always build the redistributable repository, but only build the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# nonredistributable bits if we have access to closed source.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Some objects that result from the closed build are still
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# redistributable, and should be packaged as part of an open-only
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# build. Access to those objects is provided via the closed-bins
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# tarball. See usr/src/tools/scripts/bindrop.sh for details.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The packages directory will contain the processed manifests as
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# direct build targets and subdirectories for package metadata extracted
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# incidentally during manifest processing.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Nothing underneath $(PDIR) should ever be managed by SCM.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The tools proto must be specified for dependency generation.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Publication from the tools proto area is managed in the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# publication rule.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein$(PDIR)/developer-build-onbld.dep:= PKGROOT= $(TOOLSROOT)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# To get these defaults, manifests should simply refer to $(PKGVERS).
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinPKGVERS= $(PKGVERS_COMPONENT),$(PKGVERS_BUILTON)-$(PKGVERS_BRANCH)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The ARCH32 and ARCH64 macros are used in the manifests to express
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# architecture-specific subdirectories in the installation paths
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# for isaexec'd commands.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# We can't simply use $(MACH32) and $(MACH64) here, because they're
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# only defined for the build architecture. To do cross-platform
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# packaging, we need both values.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# macros and transforms needed by pkgmogrify
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# If you append to this list using target-specific assignments (:=),
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# be very careful that the targets are of the form $(PDIR)/pkgname. If
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# you use a higher level target, or a package list, you'll trigger a
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# complete reprocessing of all manifests because they'll fail command
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# dependency checking.
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark AndrewsPM_TRANSFORMS= common_actions publish restart_fmri facets defaults \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'PLATFORM=i86hvm' \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'PLATFORM=i86pc' \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'PLATFORM=i86xpv' \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'ISALIST=amd64' \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'ISALIST=i386'
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'PLATFORM=sun4u' \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'PLATFORM=sun4v' \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'ISALIST=sparcv9' \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 'ISALIST=sparc'
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The package lists are generated with $(PKGDEP_TYPE) as their
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# dependency types, so that they can be included by either an
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# incorporation or a group package.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein$(PDIR)/osnet-incorporation.mog:= PKGDEP_TYPE= incorporate
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein depend fmri=consolidation/osnet/osnet-incorporation type=require
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# All packaging build products should go into $(PDIR), so they don't
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# need to be included separately in CLOBBERFILES.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinCLOBBERFILES= $(PDIR) proto_list_$(PKGMACH) install-$(PKGMACH).out \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# By default, PKGS will list all manifests. To build and/or publish a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# subset of packages, override this on the command line or in the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# build environment and then reference (implicitly or explicitly) the all
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# or install targets. Using ls -1 (that's a one) or print or echo to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# get the list of manifests is a little hackish, but avoids having a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# 900+ line file to explicitly list them all.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# We want some manifests to optionally built based on environment
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# options, so those are excluded and optionally added back in.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# We also want a relatively easy way to add files to the list of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# manifests given special treatment. Add any other special ones
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# to the SPECIAL_MANIFESTS vaiable. It can contain wildcards in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# regexp form, i.e. SUNW.* as one useful example.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinLIST_MANIFESTS_CMD = (cd manifests ; /usr/bin/ls -1 *.mf |\
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Conditionally add back lp-ipp
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein$(ENABLE_IPP_PRINTING) MANIFESTS += print-lp-ipp-ipp-listener.mf
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Track the synthetic manifests separately so we can properly express
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# build rules and dependencies. The synthetic and real packages use
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# different sets of transforms and macros for pkgmogrify.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Root of pkg image to use for dependency resolution
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Normally / on the machine used to build the binaries
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# For each package, we determine the target repository based on
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# manifest-embedded metadata. Because we make that determination on
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# the fly, the publication target cannot be expressed as a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# subdirectory inside the unknown-by-the-makefile target repository.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# In order to limit the target set to real files in known locations,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# we use a ".pub" file in $(PDIR) for each processed manifest, regardless
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# of content or target repository.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinPUB_PKGS= $(SYNTH_PKGS:%=$(PDIR)/%.pub) $(PKGS:%=$(PDIR)/%.pub)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Any given repository- and status-specific package list may be empty,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# but we can only determine that dynamically, so we always generate all
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# lists for each repository we're building.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The meanings of each package status are as follows:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# PKGSTAT meaning
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# ---------- ----------------------------------------------------
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# noincorp Do not include in incorporation or group package
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# obsolete Include in incorporation, but not group package
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# renamed Include in incorporation, but not group package
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# current Include in incorporation and group package
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Since the semantics of the "noincorp" package status dictate that
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# such packages are not included in the incorporation or group packages,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# there is no need to build noincorp package lists.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PROC_SYNTH_PKGS) $(DEP_SYNTH_PKGS) $(PUB_PKGS)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# For a single manifest, the dependency chain looks like this:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# raw manifest (mypkg.mf)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# | use pkgmogrify to process raw manifest
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# processed manifest (mypkg.mog)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# * | use pkgdepend generate to generate dependencies
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# manifest with TBD dependencies (mypkg.dep)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# % | use pkgdepend resolve to resolve dependencies
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# manifest with dependencies resolved (mypkg.res)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# | use pkgsend to publish the package
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# placeholder to indicate successful publication (mypkg.pub)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# * This may be suppressed via SUPPRESSPKGDEP. The resulting
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# packages will install correctly, but care must be taken to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# install all dependencies, because pkg will not have the input
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# it needs to determine this automatically.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# % This is included in this diagram to make the picture complete, but
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# this is a point of synchronization in the build process.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Dependency resolution is actually done once on the entire set of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# manifests, not on a per-package basis.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The full dependency chain for generating everything that needs to be
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# published, without actually publishing it, looks like this:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# processed synthetic packages
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# package lists synthetic package manifests
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# processed real packages
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# package dir real package manifests
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Here, each item is a set of real or synthetic packages. For this
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# portion of the build, no reference is made to the proto area. It is
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# therefore suitable for the "all" target, as opposed to "install."
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Since each of these steps is expressed explicitly, "all" need only
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# depend on the head of the chain.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# From the end of manifest processing, the publication dependency
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# chain looks like this:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# repository metadata (catalogs and search indices)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# | pkgrepo refresh
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# published packages
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# | | pkgsend publish
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# repositories resolved dependencies
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# pkgsend | | pkgdepend resolve
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# create-repository |
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# | generated dependencies
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# repo directories |
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# | pkgdepend
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# processed manifests
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinALL_TARGETS= $(PROC_SYNTH_PKGS) proto_list_$(PKGMACH)
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# This will build the directory to contain the processed manifests
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews# and the metadata symlinks.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# This rule resolves dependencies across all published manifests.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# We shouldn't have to ignore the error from pkgdepend, but until
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# 16012 and its dependencies are resolved, pkgdepend will always exit
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# with an error.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein -$(PKGDEBUG)if [ "$(SUPPRESSPKGDEP)" = "true" ]; then \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "Suppressing dependency resolution"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "Resolving dependencies"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein for p in $(DEP_SYNTH_PKGS:%.dep=%) $(DEP_PKGS:%.dep=%); do \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "Removing dependency versions from $$p"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Since we create zero-length processed manifests for a graceful abort
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# from pkgmogrify, we need to detect that here and make no effort to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# publish the package.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# For all other packages, we publish them regardless of status. We
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# derive the target repository as a component of the metadata-derived
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# symlink for each package.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinpublish_pkgs: $(REPOS:%=$(PKGDEST)/repo.%) $(PDIR)/gendeps .WAIT $(PUB_PKGS)
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce# Before publishing, we want to pull the license files from $CODEMGR_WS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# into the proto area. This allows us to NOT pass $SRC (or
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# $CODEMGR_WS) as a basedir for publication.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Initialize the empty on-disk repositories
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)pkgsend -s file://$(@) create-repository \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# rule to process real manifests
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# To allow redistributability and package status to change, we must
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# remove not only the actual build target (the processed manifest), but
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# also the incidental ones (the metadata-derived symlinks).
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# If pkgmogrify exits cleanly but fails to create the specified output
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# file, it means that it encountered an abort directive. That means
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# that this package should not be published for this particular build
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# environment. Since we can't prune such packages from $(PKGS)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# retroactively, we need to create an empty target file to keep make
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# from trying to rebuild it every time. For these empty targets, we
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# do not create metadata symlinks.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Automatic dependency resolution to files is also done at this phase of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# processing. The skipped packages are skipped due to existing bugs
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# in pkgdepend.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The incorporation dependency is tricky: it needs to go into all
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# current and renamed manifests (ie all incorporated packages), but we
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# don't know which those are until after we run pkgmogrify. So
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# instead of expressing it as a transform, we tack it on ex post facto.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Implementation notes:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# - The first $(RM) must not match other manifests, or we'll run into
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# race conditions with parallel manifest processing.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# - The make macros [ie $(MACRO)] are evaluated when the makefile is
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# read in, and will result in a fixed, macro-expanded rule for each
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# target enumerated in $(PROC_PKGS).
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# - The shell variables (ie $$VAR) are assigned on the fly, as the rule
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# is executed. The results may only be referenced in the shell in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# which they are assigned, so from the perspective of make, all code
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# that needs these variables needs to be part of the same line of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# code. Hence the use of command separators and line continuation
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# characters.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# - The extract_metadata transforms are designed to spit out shell
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# variable assignments to stdout. Those are published to the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# .vars temporary files, and then used as input to the eval
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# statement. This is done in stages specifically so that pkgmogrify
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# can signal failure if the manifest has a syntactic or other error.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The eval statement should begin with the default values, and the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# output from pkgmogrify (if any) should be in the form of a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# variable assignment to override those defaults.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# - When this rule completes execution, it must leave an updated
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# target file ($@) in place, or make will reprocess the package
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# every time it encounters it as a dependency. Hence the "touch"
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# statement to ensure that the target is created, even when
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# pkgmogrify encounters an abort in the publish transforms.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)$(RM) $(@) $(@:%.mog=%) $(@:%.mog=%.nodepend) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(@:%.mog=%.lics) $(PDIR)/$(@F:%.mog=%).metadata.* $(@).vars
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)$(PKGMOGRIFY) $(PKGMOG_VERBOSE) $(PM_INC:%= -I %) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)eval REPO=redist PKGSTAT=current NODEPEND=$(SUPPRESSPKGDEP) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein if [ -f $(@) ]; then \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PDIR)/$(@F:%.mog=%).metadata.$$PKGSTAT.$$REPO; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)if [ ! -f $(@:%.dep=%.nodepend) ]; then \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein pkgdepend generate -m $(PKGDEP_TOKENS:%=-D %) $(<) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The full chain implies that there should be a .dep.res suffix rule,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# but dependency generation is done on a set of manifests, rather than
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# on a per-manifest basis. Instead, see the gendeps rule above.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)m=$$(basename $(@:%.pub=%).metadata.*); \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein r=$${m#$(@F:%.pub=%.metadata.)+(?).}; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein if [ -s $(<) ]; then \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "Publishing $(@F:%.pub=%) to $$r repository"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein --fmri-in-manifest --no-index --no-catalog $(<) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# rule to build the synthetic manifests
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# This rule necessarily has PKGDEP_TYPE that changes according to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# the specific synthetic manifest. Rather than escape command
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# dependency checking for the real manifest processing, or failing to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# express the (indirect) dependency of synthetic manifests on real
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# manifests, we simply split this rule out from the one above.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The implementation notes from the previous rule are applicable
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein$(PROC_SYNTH_PKGS): $(PKGLISTS) $$(@F:%.mog=%.mf)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein @print "Processing synthetic manifest $(@F:%.mog=%.mf)"
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)$(RM) $(@) $(PDIR)/$(@F:%.mog=%).metadata.* $(@).vars
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)$(PKGMOGRIFY) $(PKGMOG_VERBOSE) -I transforms -I $(PDIR) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGMOG_DEFINES:%=-D %) -D PKGDEP_TYPE=$(PKGDEP_TYPE) \
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce $(PKGDEBUG)eval REPO=redist PKGSTAT=current `$(CAT) -s $(@).vars`; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein if [ -f $(@) ]; then \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PDIR)/$(@F:%.mog=%).metadata.$$PKGSTAT.$$REPO; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein @print "Skipping dependency generation for $(@F:%.dep=%)"
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce# This rule assumes that all links in the $PKGSTAT directories
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# point to valid manifests, and will fail the make run if one
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# does not contain an fmri.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# We do this in the BEGIN action instead of using pattern matching
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# because we expect the fmri to be at or near the first line of each input
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# file, and this way lets us avoid reading the rest of the file after we
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# find what we need.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# We keep track of a failure to locate an fmri, so we can fail the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# make run, but we still attempt to process each package in the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# repo/pkgstat-specific subdir, in hopes of maybe giving some
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# additional useful info.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The protolist is used for bfu archive creation, which may be invoked
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# interactively by the user. Both protolist and PKGLISTS targets
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# depend on $(PROC_PKGS), but protolist builds them recursively.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# To avoid collisions, we insert protolist into the dependency chain
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# here. This has two somewhat subtle benefits: it allows bfu archive
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# creation to work correctly, even when -a was not part of NIGHTLY_OPTIONS,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# and it ensures that a protolist file here will always correspond to the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# contents of the processed manifests, which can vary depending on build
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# environment.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "Generating $$r $$s package list"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein if (ARGC < 2) { \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein retcode = 0; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein for (i = 1; i < ARGC; i++) { \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein e = getline f < ARGV[i]; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein } while ((e == 1) && (f !~ /name=pkg.fmri/)); \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein close(ARGV[i]); \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein if (e == 1) { \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein l = split(f, a, "="); \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "depend fmri=" a[l], \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein "type=$$(PKGDEP_TYPE)"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "no fmri in " ARGV[i] >> "/dev/stderr"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein retcode = 2; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein exit retcode; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein }' `find $(PDIR) -type l -a \( $(PKGS:%=-name %.metadata.$$s.$$r -o) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# rules to validate proto area against manifests, check for safe
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# file permission modes, and generate a faux proto list
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# For the check targets, the dependencies on $(PROC_PKGS) is specified
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# as a subordinate make process in order to suppress output.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# The .lics files were created during pkgmogrification, and list the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# set of licenses to pull from $SRC for each package. Because
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# licenses may be duplicated between packages, we uniquify them as
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# well as aggregating them here.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(PKGDEBUG)( for l in `cat $(PROC_PKGS:%.mog=%.lics)`; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Staging the license and description files in the proto area allows
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# us to do proper unreferenced file checking of both license and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# description files without blanket exceptions, and to pull license
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# content without reference to $CODEMGR_WS during publication.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein PKGDEBUG=$(PKGDEBUG) LICROOT=$(PKGROOT)/licenses \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "$(PKGROOT)/licenses/" $$0; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein print "$(PKGROOT)/licenses/" $$0 ".descrip"; \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(EXCEPTIONS:%=-e $(CODEMGR_WS)/exception_lists/%) \
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein @validate_pkg -a $(PKGMACH) -L -m $(PDIR) > $(@)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# This is a convenience target to allow package names to function as
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# build targets. Generally, using it is only useful when iterating on
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# development of a manifest.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# When processing a manifest, use the basename (without extension) of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# the package. When publishing, use the basename with a ".pub"
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Other than during manifest development, the preferred usage is to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# avoid these targets and override PKGS on the make command line and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# use the provided all and install targets.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein$(PKGS:%=%.pub) $(SYNTH_PKGS:%=%.pub): $(PDIR)/$$(@)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# This is a convenience target to resolve dependencies without publishing
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# These are convenience targets for cross-platform packaging. If you
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# want to build any of "the normal" targets for a different
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# architecture, simply use "arch/target" as your build target.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# Since the most common use case for this is "install," the architecture
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein# specific install targets have been further abbreviated to elide "/install."
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein $(MAKE) -e $(@F) PKGMACH=$(@D) SUPPRESSPKGDEP=$(SUPPRESSPKGDEP)