--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pkg/.gitignore	Sun Jul 02 16:08:13 2017 +0300
@@ -0,0 +1,1 @@
+packages.i386

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pkg/Makefile	Sun Jul 02 16:08:13 2017 +0300
@@ -0,0 +1,63 @@
+.include <unleashed.mk>
+.include <${SRCTOP}/Makefile.cfgparam>
+
+PRE_POUND=pre\#
+POUND_SIGN=$(PRE_POUND:pre%=%)
+
+INCS = \
+	transforms \
+	manifests
+
+DEFS = \
+	i386_ONLY=$(POUND_SIGN) \
+	sparc_ONLY=$(POUND_SIGN) \
+	i86pc_ONLY=$(POUND_SIGN) \
+	i86xpv_ONLY=$(POUND_SIGN) \
+	sun4u_ONLY=$(POUND_SIGN) \
+	sun4v_ONLY=$(POUND_SIGN) \
+	$(CONFIG_MACH)_ONLY= \
+	$(CONFIG_PLATFORM)_ONLY= \
+	CONFIG_PLATFORM=$(CONFIG_PLATFORM) \
+	ARCH=$(CONFIG_MACH) \
+	ARCH32=$(CONFIG_MACH32) \
+	ARCH64=$(CONFIG_MACH64) \
+	PKGVERS_COMPONENT=$(PKGVERS_COMPONENT) \
+	PKGVERS_BUILTON=$(PKGVERS_BUILTON) \
+	PKGVERS_BRANCH=$(PKGVERS_BRANCH) \
+	PKGVERS=$(PKGVERS) \
+	ENABLE_PERL64=$(ENABLE_PERL64) \
+	PERL_ARCH=$(PERL_ARCH) \
+	PERL_ARCH64=$(PERL_ARCH64) \
+	PERL_VERSION=$(PERL_VERSION) \
+	PERL_PKGVERS=$(PERL_PKGVERS) \
+	PYTHON_VERSION=$(PYTHON_VERSION) \
+	PYTHON_PKGVERS=$(PYTHON_PKGVERS) \
+	HUMAN_VERSION=$(VERSION)
+
+TRANSFORMS=common_actions \
+	   publish \
+	   restart_fmri \
+	   facets \
+	   defaults \
+	   extract_metadata
+
+all: generate-pseudo
+
+clean:
+
+generate-pseudo:
+	${SRCTOP}/tools/gen-pkg-manifest.sh
+
+.PHONY: all clean generate-pseudo
+
+.SUFFIXES: .mf .mog .dep
+
+.mf.mog: ${TRANSFORMS:%=transforms/%}
+	@echo fixme
+	pkgmogrify ${INCS:%=-I %} ${DEFS:%=-D %} -P ${.TARGET}.vars \
+		-O ${.TARGET} ${.IMPSRC} ${TRANSFORMS}
+
+.mog.dep:
+	@echo fixme
+	pkgdepend generate
+

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pkg/Makefile.lic	Sun Jul 02 16:08:13 2017 +0300
@@ -0,0 +1,47 @@
+#
+# CDDL HEADER START
+#
+# The contents of this file are subject to the terms of the
+# Common Development and Distribution License (the "License").
+# You may not use this file except in compliance with the License.
+#
+# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
+# or http://www.opensolaris.org/os/licensing.
+# See the License for the specific language governing permissions
+# and limitations under the License.
+#
+# When distributing Covered Code, include this CDDL HEADER in each
+# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
+# If applicable, add the following below this CDDL HEADER, with the
+# fields enclosed by brackets "[]" replaced with your own identifying
+# information: Portions Copyright [yyyy] [name of copyright owner]
+#
+# CDDL HEADER END
+#
+
+#
+# Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
+#
+
+#
+# PKGDEBUG and LICROOT should be defined on the command line or in
+# the environment when using this Makefile, as they generally come
+# from usr/src/pkg/Makefile.  The remaining env vars should already
+# be part of a working build environment.
+#
+
+include $(SRC)/Makefile.master
+
+#
+# For license files in the open source tree, always copy them from src
+# into the license staging directory in the proto area
+#
+$(LICROOT)/usr/src/%: $(SRCTOP)/usr/src/%
+	$(PKGDEBUG)if [ ! -d $(@D) ]; then mkdir -p $(@D); fi
+	$(PKGDEBUG)$(INS.file)
+
+# this is a terrible hack, we're reaching into bmake-build source tree to
+# grab the license file
+$(LICROOT)/%: $(SRCTOP)/%
+	$(PKGDEBUG)if [ ! -d $(@D) ]; then mkdir -p $(@D); fi
+	$(PKGDEBUG)$(INS.file)

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

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pkg/README.pkg	Sun Jul 02 16:08:13 2017 +0300
@@ -0,0 +1,465 @@
+#
+# CDDL HEADER START
+#
+# The contents of this file are subject to the terms of the
+# Common Development and Distribution License (the "License").
+# You may not use this file except in compliance with the License.
+#
+# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
+# or http://www.opensolaris.org/os/licensing.
+# See the License for the specific language governing permissions
+# and limitations under the License.
+#
+# When distributing Covered Code, include this CDDL HEADER in each
+# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
+# If applicable, add the following below this CDDL HEADER, with the
+# fields enclosed by brackets "[]" replaced with your own identifying
+# information: Portions Copyright [yyyy] [name of copyright owner]
+#
+# CDDL HEADER END
+#
+
+#
+# Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
+#
+
+Introduction
+------------
+
+This README describes some basics about creating, modifying, and
+building packages in ON.  All package creation in ON is done using
+tools available to our customers.  If terminology in this document
+is confusing, you may wish to review the pkg(5) manpage.
+
+Packaging Overview
+------------------
+
+usr/src/pkg/ contains the definitions and rules needed to build an IPS
+repository which contain the deliverables from an ON build.
+
+The manifests directory contains all manifests, and has one file
+per package.  For most packaging changes you only need to add or
+change the packaging manifests themselves.
+
+The build rules create a package repository.  Separate DEBUG and
+non-DEBUG versions are built, and are available at:
+    $SRCTOP/packages/$MACH/nightly[-nd]/repo.redist
+
+Building Packages
+-----------------
+
+The -p option to nightly will build the IPS repository.
+
+Alternatively, in usr/src/pkg/Makefile there are make targets for:
+
+	all
+	    Process manifests into their final form with unresolved
+	    dependencies before publication.
+
+	install
+	    Publish packages.
+
+	gendeps
+	    Run `pkgdepend resolve`.  See Dependencies section.
+
+	protocmp
+	    Compare the proto area against package definitions for
+	    missing or incorrect files.
+
+	pmodes
+	    Check file and directory modes for best practices.
+
+	check
+	    Run protocmp and pmodes.
+
+The build behavior may modified by the following variables:
+
+	SUPPRESSPKGDEP
+	    If SUPPRESSPKGDEP is set to "true" in your environment,
+	    package dependencies will not be generated.  This variable
+	    should not be set in normal builds as it will mask product
+	    bugs.
+
+	PKGDEBUG
+	    If PKGDEBUG is set in your environment, $MAKE will print
+	    detailed information about the commands it executes to
+	    process and publish packages.
+
+	ONNV_BUILDNUM
+	    If ONNV_BUILDNUM is set to an older ON build number,
+	    your packages will be published at that version instead
+	    of the one defined in usr/src/Makefile.buildnum, which
+	    is managed by the gatekeepers.
+
+A set of intermediate build products are placed in
+usr/src/pkg/packages.$MACH/.  These can be useful during development.
+
+	.mog
+	    The resulting package manifest after running pkgmogrify(1)
+	    on the supplied manifest.  See below for details on
+	    pkgmogrify(1) use in ON.
+
+	.dep
+	    The resulting manifest after running `pkgdepend generate`
+	    on the .mog manifest.
+
+	.res
+	    The resulting manifest after running `pkgdepend resolve`
+	    on the .dep manifest.
+
+Incremental Builds
+------------------
+
+   If you want to process a subset of manifests, simply set PKGS on the
+   make command line and specify the "all" target.  If you want to process
+   them all, simply specify the "all" target.
+
+   	% dmake -e PKGS="BRCMbnx BRCMbnxe" all
+	% dmake -e all
+
+   If you want to publish a subset of packages, simply set PKGS on the
+   make command line and specify the "install" target.  Overriding PKGS
+   will cause dependency resolution to be limited to PKGS from the
+   current build, with a fallback to packages installed on the build
+   system.  If you want to publish them all, simply specify the
+   "install" target.
+
+   	% dmake -e PKGS="BRCMbnx BRCMbnxe" install
+	% dmake -e install
+
+   You can also use package names, or package names with ".pub"
+   extensions, as build targets.  This will cause processing or
+   publication of the specified package(s).
+
+   The on-disk repository will be initialized when it does not exist,
+   or when you run nightly -p.  If you build incrementally,
+   packages will simply be added to the existing repository.
+
+   To do cross-platform packaging, prefix your target with (for
+   example) "sparc/", as in "dmake sparc/install".  Note that we
+   currently pull some license files directly from a built source
+   tree, so if you do this in a workspace that had proto area copied
+   in via nightly -U, then you'll need to set $SRC to point to the
+   workspace that was actually built.
+
+Testing Packages
+----------------
+
+To test the generated repository, you should use the "onu" tool
+available from /opt/onbld/bin or usr/src/tools/scripts/ to setup and
+upgrade your system.  A manpage is available in /opt/onbld/man
+or usr/src/tools/scripts/onu.1.
+
+Alternatively, you can manually start a pkg.depot(1M) server to
+serve the generated repository to multiple test machines.
+
+	Start up a depot on your build machine.
+	    cd $SRCTOP/packages/$MACH/nightly[-nd]
+	    /usr/lib/pkg.depotd -d repo.redist -p <port> &
+
+	    Make SURE you choose an unused port and the depot
+	    starts successfully.
+
+	    The depot can be started across NFS as well if you
+	    have a fast pipe.
+
+	Configure your test system.
+	    pkg set-publisher -P -g http://<your server host>:<port> on-nightly
+	    pkg set-publisher --non-sticky opensolaris.org
+	    pkg uninstall entire
+
+	pkg image-update your test system.
+	    pkg image-update will upgrade all packages on your test system
+
+Always make sure your bits are installed with image-update.
+	Check your versions.
+	    pkg info osnet-incorporation
+
+	Multiple packages should be updated.
+	    If you did a full build, all ON packages will be updated.
+	    When image-update tells you that only one or two packages has
+	    been updated, you likely did not get the updates you expected.
+
+There are various tactics for troubleshooting a failed upgrade.
+	Make sure entire is uninstalled.
+
+	pkg install -nv osnet-incorporation@<your version>
+	    Ask IPS to explicitly check if ON can be installed, and
+	    if it can't, tell you why not.
+
+	Obsolete and renamed packages can cause trouble.
+	    pkg search -l ::pkg.renamed:true
+	    pkg search -l ::pkg.obsolete:true
+
+
+Making Packaging Changes
+------------------------
+
+Package definitions are in usr/src/pkg/manifests/, and have one
+file per package, including for multi-architecture packages.  For
+most packaging changes you only need to add or change the packaging
+manifests themselves.  No packaging metadata may be kept outside of the
+manifests. If you find yourself needing to modify usr/src/pkg/Makefile,
+you're almost certainly doing something wrong.
+
+Remember that the "check" target is available to check many of
+your packaging changes.
+
+We run pkgmogrify(1) over the manifests before publication.  This
+allows us to apply a set of macros and package transformations in
+order to make the manifests themselves easier to maintain.
+
+We supply a set of commonly-used macros for use in package manifests.
+These are the PKGMOG_DEFINES in usr/src/pkg/Makefile.
+
+	$(i386_ONLY)
+	$(ARCH)
+	$(ARCH32)
+	$(ARCH64)
+	$(PKGVERS), which is set to
+	   $(PKGVERS_COMPONENT),$(PKGVERS_BUILTON)$(PKGVERS_BRANCH)
+
+pkgmogrify(1) also allows us to include a set of default transformations.
+The definitions for these transforms are in usr/src/pkg/transforms/.  An
+overview of their use is supplied here, but for a full accounting, please
+read pkmogrify(1) and the files themselves.
+
+	defaults
+	    This transform is applied to all manifests.  It specifies
+	    a set of sensible default permissions, a set of
+	    directory locations for which the reboot-needed actuator
+	    is always applied to files, and some other basic defaults.
+
+	publish
+	    This transform is applied to all manifests.  It ensures
+	    that manifest lines which don't apply to the current
+	    architecture are stripped.
+
+	restart_fmri
+	    This transform is applied to all manifests.  It modifies
+	    all package manifest lines for SMF manifests in standard
+	    locations to include an actuator which runs manifest-import
+	    on installation/update/removal, as well as some others.  If
+	    you're adding a new class of file that would benefit from
+	    a restart or refresh of a specific SMF service, please add
+	    it here.
+
+	extract_metadata
+	    This transform is applied to all manifests.  It deals with
+	    manipulations required for packaging metadata like
+	    pkg.renamed, and pkg.obsolete.
+
+	hollow_zone_pkg
+	    This transform is available for explicit inclusion in
+	    some manifests.  It ensures that all contents of the
+	    package are not installed within a non-global zone, but the
+	    package and its metadata are available in order to satisfy
+	    packaging dependencies.
+
+pkgmogrify(1) also allows us to use comments and continuation lines
+in our manifests.
+
+Zones and Packages
+------------------
+
+pkg(5) uses variants to implement zones.  If a package is marked
+with both global and non-global zone variants, the package contents will
+be installed in both global and non-global by default.
+	set name=variant.opensolaris.zone value=global value=nonglobal
+
+Specific actions within a package can be tagged as applying to only
+the global zone or only the non-global zones.
+
+The hollow_zone_pkg transform described above is also available to
+simplify a common packaging scenario.
+
+Dependencies
+------------
+
+Package dependencies are automatically calculated during build time
+using pkgdepend(1).  After you've done a build, you can verify your
+dependencies in the <package>.res file described above.  If the
+file is missing a dependency that you believe could be auto-detected,
+please file a bug against pkgdepend(1).
+
+Dependencies can be added manually using the "depend" action.  Please
+add a comment describing why the dependency is required.
+
+Moving Content Between Packages and Removing Content
+----------------------------------------------------
+
+pkg(5) tracks when content is removed from packages, and automatically
+removes it.
+
+If you need to move content between packages, there are two primary
+things to do.
+
+	"preserve" files must be marked with original_name.
+	    The first time a "preserve" file moves between packages,
+	    you must set original_name=<original package>:<file>
+	    in that file's action.  Subsequent moves do not require
+	    modification.
+
+	Consider adding a dependency on the new package.
+	    The only way a system will end up with a new package
+	    after upgrade is if an existing package depends on it.
+
+Renaming a Package
+------------------
+
+To rename a package, leave the old package manifest in place, but
+empty it of all delivered content.  The old package should include:
+
+	set name=pkg.fmri with the version set explicitly to the
+	    build you're integrating into.  For example, if you wanted
+	    to rename SUNWrmodu in build 133 you'd change the pkg.fmri
+	    line to read
+	    set name=pkg.fmri value=pkg:/SUNWrmodu@0.5.11,5.11-0.133
+
+	set name=pkg.renamed value=true
+
+	The architectures and variants you're renaming.  These
+	    should just be copied from your old package, as you
+	    must rename a package on all architectures and
+	    variants simultaneously.
+
+	A dependency on the new package.
+
+If there were "preserve" files in the package you're renaming, make
+sure to create original_name settings in the new package.
+
+If there was a org.opensolaris.noincorp property in the package being
+renamed, make sure you keep it in both the original and the renamed
+packages.
+
+EOFs and Removals
+-----------------
+
+To remove files, directories, drivers, or anything else within a package,
+simply stop delivering them in the package.  IPS will manage the removal
+of no longer delivered content.
+
+Package removals have impact on the rest of the system.  Before marking
+a package as obsolete, search in the OpenSolaris development
+repository (http://pkg.opensolaris.org/dev or http://ipkg.sfbay/dev)
+to find out if any other packages depend on the software you intend
+to EOF.  If any packages do, you need to coordinate with those
+consolidations.
+
+The "slim_install" package may depend on ON packages.  If it does,
+you must send a FLAG DAY message for ON users and PIT who test
+install.  You must also file an installation bug to get that package
+updated in the same build or earlier than you intend to integrate.
+You should also test install yourself.  You can do this by replacing
+the "slim_install" in your Distro Constructor manifest with the
+explicit list of packages to install.
+
+To remove a package, you must mark it as obsolete.  You must *also* mark
+as obsolete any packages which are renamed ancestors of this package, and
+remove their rename dependencies.  Here is what you must do.
+
+To find rename ancestors, select all of the manifests which are renames,
+then look for the one which was renamed to the package you care about.
+For example, to find rename ancestors of 'system/zones', do the following:
+
+    $ cd usr/src/pkg/manifests
+    $ mypkgname=system/zones
+    $ grep -l "fmri=pkg:/$mypkgname@" `grep -l pkg.renamed *.mf` /dev/null
+    SUNWzone.mf
+
+Make sure to check that the package has not undergone multiple renames!
+
+    $ mypkgname=SUNWzone
+    $ grep -l "fmri=pkg:/$mypkgname@" `grep -l pkg.renamed *.mf` /dev/null
+    $
+
+Once you have the renamed ancestor list, for *each* of the packages (the
+newly obsolete package, and its renamed ancestors), edit the package as
+follows:
+
+	Update 'set name=pkg.fmri' with the version set explicitly to the
+	    build you're integrating into.  For example, if you wanted
+	    to remove SUNWwbsd in build 133 you'd change the pkg.fmri
+	    line to read:
+	    'set name=pkg.fmri value=pkg:/SUNWwbsd@0.5.11,5.11-0.133'
+
+	Add 'set name=pkg.obsolete value=true'.
+
+	Maintain the architecture and variant declarations in the
+	    package you are obsoleting.  Note that you must obsolete a
+	    package on all architectures and variants simultaneously.
+
+	Delete everything else.
+
+	If the package is a renamed ancestor, leave a comment behind as
+        follows:
+
+	   # Was renamed to <other-pkg-name>, both now obsolete.
+
+Here is a complete example.  SUNWfoobar was a package which was renamed
+to system/foobar in build 140, and then later obsoleted in build 150.
+Note that in all cases the package FMRI is updated to the obsoletion
+build, 150.
+
+    SUNWfoobar.mf:
+        # Was renamed to system/foobar, both now obsolete.
+        set name=pkg.fmri value=pkg:/SUNWfoobar@0.5.11,5.11-0.150
+        set name=pkg.obsolete value=true
+        set name=variant.arch value=$(ARCH)
+
+    system-foobar.mf:
+	set name=pkg.fmri value=pkg:/system/foobar@0.5.11,5.11-0.150
+	set name=pkg.obsolete value=true
+	set name=variant.arch value=$(ARCH)
+
+Creating a Package
+------------------
+
+The easiest thing is to copy a package similar to the one you're
+trying to create.  Note that packages are no longer split on the
+/usr and / boundary.
+
+The following actions are required for all packages in ON.
+	set name=pkg.fmri
+	    Every package must have an FMRI.  That is the package's
+	    name.
+
+	set name=pkg.summary
+	    Every package must have a short summary of its purpose.
+
+	set name=pkg.description
+	    Every package must have a one-sentence description of
+	    its purpose.
+
+	set name=variant.arch
+	    Every package must specify which architectures it delivers.
+
+	set name=info.classification
+	    Every package must specify a category for the packaging GUI.
+	    You must use an existing category, and may not invent new ones.
+	    Existing categories and their subcategories are listed
+	    in /usr/share/package-manager/data/opensolaris.org.sections.
+
+	license
+	    All packages must specify a set of license actions.  If
+	    you're adding items here that are not already included in
+	    usr/src/pkg/license_files, then you will also need to modify 
+	    usr/src/tools/opensolaris/license-list.
+
+You don't need to set the following.  They're taken care of for all OS/Net
+packages in the transforms/common_actions file.
+
+	set name=variant.opensolaris.zone
+	    Every package must specify whether it can be installed in
+	    global zones, non-global zones, or both.  All ON packages are
+	    delivered in both global and non-global zones.
+
+	set name=org.opensolaris.consolidation value=osnet
+	    All packages from OS/Net come from OS/Net...
+
+Drivers and Packages
+--------------------
+
+Scripting is no longer required to deal with addition or removal of
+drivers in ON.  A "driver" action should be specified for each driver,
+and IPS will handle updates to all the driver files.