Lines Matching refs:packages

30 building packages in ON.  All package creation in ON is done using
46     $CODEMGR_WS/packages/$MACH/nightly[-nd]/repo.redist
60 	    Publish packages.
86 	    process and publish packages.
89 usr/src/pkg/packages.$MACH/.  These can be useful during development.
114    If you want to publish a subset of packages, simply set PKGS on the
117    current build, with a fallback to packages installed on the build
130    packages will simply be added to the existing repository.
151 	    cd $CODEMGR_WS/packages/$MACH/nightly[-nd]
166 	    pkg image-update will upgrade all packages on your test system
172 	Multiple packages should be updated.
173 	    If you did a full build, all ON packages will be updated.
174 	    When image-update tells you that only one or two packages has
184 	Obsolete and renamed packages can cause trouble.
193 file per package, including for multi-architecture packages.  For
285 pkg(7) tracks when content is removed from packages, and automatically
288 If you need to move content between packages, there are two primary
292 	    The first time a "preserve" file moves between packages,
327 packages.
339 to find out if any other packages depend on the software you intend
340 to EOF.  If any packages do, you need to coordinate with those
343 The "slim_install" package may depend on ON packages.  If it does,
349 explicit list of packages to install.
352 as obsolete any packages which are renamed ancestors of this package, and
370 Once you have the renamed ancestor list, for *each* of the packages (the
413 trying to create.  Note that packages are no longer split on the
416 The following actions are required for all packages in ON.
438 	    All packages must specify a set of license actions.
441 packages in the transforms/common_actions file.
445 	    global zones, non-global zones, or both.  All ON packages are
449 	    All packages from OS/Net come from OS/Net...