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.
90 	    your packages will be published at that version instead
95 usr/src/pkg/packages.$MACH/.  These can be useful during development.
120    If you want to publish a subset of packages, simply set PKGS on the
123    current build, with a fallback to packages installed on the build
136    packages will simply be added to the existing repository.
157 	    cd $CODEMGR_WS/packages/$MACH/nightly[-nd]
172 	    pkg image-update will upgrade all packages on your test system
178 	Multiple packages should be updated.
179 	    If you did a full build, all ON packages will be updated.
180 	    When image-update tells you that only one or two packages has
190 	Obsolete and renamed packages can cause trouble.
199 file per package, including for multi-architecture packages.  For
292 pkg(5) tracks when content is removed from packages, and automatically
295 If you need to move content between packages, there are two primary
299 	    The first time a "preserve" file moves between packages,
334 packages.
346 to find out if any other packages depend on the software you intend
347 to EOF.  If any packages do, you need to coordinate with those
350 The "slim_install" package may depend on ON packages.  If it does,
356 explicit list of packages to install.
359 as obsolete any packages which are renamed ancestors of this package, and
377 Once you have the renamed ancestor list, for *each* of the packages (the
420 trying to create.  Note that packages are no longer split on the
423 The following actions are required for all packages in ON.
445 	    All packages must specify a set of license actions.  If
451 packages in the transforms/common_actions file.
455 	    global zones, non-global zones, or both.  All ON packages are
459 	    All packages from OS/Net come from OS/Net...