Lines Matching refs:package
30 building packages in ON. All package creation in ON is done using
42 per package. For most packaging changes you only need to add or
81 Compare the proto area against package definitions for
111 package dependencies will not be generated. This variable
130 The resulting package manifest after running pkgmogrify(1)
162 You can also use package names, or package names with ".pub"
164 publication of the specified package(s).
239 driver/crypto/dprov package.
246 file per package, including for multi-architecture packages. For
256 allows us to apply a set of macros and package transformations in
259 We supply a set of commonly-used macros for use in package manifests.
289 all package manifest lines for SMF manifests in standard
304 package are not installed within a non-global zone, but the
305 package and its metadata are available in order to satisfy
314 pkg(5) uses variants to implement zones. If a package is marked
315 with both global and non-global zone variants, the package contents will
319 Specific actions within a package can be tagged as applying to only
330 dependencies in the <package>.res file described above. If the
348 you must set original_name=<original package>:<file>
352 Consider adding a dependency on the new package.
353 The only way a system will end up with a new package
354 after upgrade is if an existing package depends on it.
359 To rename a package, leave the old package manifest in place, but
360 empty it of all delivered content. The old package should include:
371 should just be copied from your old package, as you
372 must rename a package on all architectures and
375 A dependency on the new package.
377 If there were "preserve" files in the package you're renaming, make
378 sure to create original_name settings in the new package.
380 If there was a org.opensolaris.noincorp property in the package being
387 To remove files, directories, drivers, or anything else within a package,
388 simply stop delivering them in the package. IPS will manage the removal
392 a package as obsolete, search in the OpenSolaris development
398 The "slim_install" package may depend on ON packages. If it does,
400 install. You must also file an installation bug to get that package
406 To remove a package, you must mark it as obsolete. You must *also* mark
407 as obsolete any packages which are renamed ancestors of this package, and
411 then look for the one which was renamed to the package you care about.
419 Make sure to check that the package has not undergone multiple renames!
426 newly obsolete package, and its renamed ancestors), edit the package as
438 package you are obsoleting. Note that you must obsolete a
439 package on all architectures and variants simultaneously.
445 If the package is a renamed ancestor, leave a comment behind as
450 Here is a complete example. SUNWfoobar was a package which was renamed
452 Note that in all cases the package FMRI is updated to the obsoletion
469 The easiest thing is to copy a package similar to the one you're
475 Every package must have an FMRI. That is the package's
479 Every package must have a short summary of its purpose.
482 Every package must have a one-sentence description of
486 Every package must specify which architectures it delivers.
489 Every package must specify a category for the packaging GUI.
492 in /usr/share/package-manager/data/opensolaris.org.sections.
503 This may be set to nonredist or internal. If a package
507 content to a package with this action, you should have
514 Every package must specify whether it can be installed in