Lines Matching refs:package
30 building packages in ON. All package creation in ON is done using
41 per package. For most packaging changes you only need to add or
44 The build rules create a package repository. Separate DEBUG and
66 Compare the proto area against package definitions for
79 package dependencies will not be generated. This variable
92 The resulting package manifest after running pkgmogrify(1)
124 You can also use package names, or package names with ".pub"
126 publication of the specified package(s).
193 file per package, including for multi-architecture packages. For
203 allows us to apply a set of macros and package transformations in
206 We supply a set of commonly-used macros for use in package manifests.
234 all package manifest lines for SMF manifests in standard
249 package are not installed within a non-global zone, but the
250 package and its metadata are available in order to satisfy
259 pkg(7) uses variants to implement zones. If a package is marked
260 with both global and non-global zone variants, the package contents will
264 Specific actions within a package can be tagged as applying to only
275 dependencies in the <package>.res file described above. If the
293 you must set original_name=<original package>:<file>
297 Consider adding a dependency on the new package.
298 The only way a system will end up with a new package
299 after upgrade is if an existing package depends on it.
304 To rename a package, leave the old package manifest in place, but
305 empty it of all delivered content. The old package should include:
316 should just be copied from your old package, as you
317 must rename a package on all architectures and
320 A dependency on the new package.
322 If there were "preserve" files in the package you're renaming, make
323 sure to create original_name settings in the new package.
325 If there was a org.opensolaris.noincorp property in the package being
332 To remove files, directories, drivers, or anything else within a package,
333 simply stop delivering them in the package. IPS will manage the removal
337 a package as obsolete, search in the OpenSolaris development
343 The "slim_install" package may depend on ON packages. If it does,
345 install. You must also file an installation bug to get that package
351 To remove a package, you must mark it as obsolete. You must *also* mark
352 as obsolete any packages which are renamed ancestors of this package, and
356 then look for the one which was renamed to the package you care about.
364 Make sure to check that the package has not undergone multiple renames!
371 newly obsolete package, and its renamed ancestors), edit the package as
383 package you are obsoleting. Note that you must obsolete a
384 package on all architectures and variants simultaneously.
388 If the package is a renamed ancestor, leave a comment behind as
393 Here is a complete example. SUNWfoobar was a package which was renamed
395 Note that in all cases the package FMRI is updated to the obsoletion
412 The easiest thing is to copy a package similar to the one you're
418 Every package must have an FMRI. That is the package's
422 Every package must have a short summary of its purpose.
425 Every package must have a one-sentence description of
429 Every package must specify which architectures it delivers.
432 Every package must specify a category for the packaging GUI.
435 in /usr/share/package-manager/data/opensolaris.org.sections.
444 Every package must specify whether it can be installed in