How to Limit Upgrades Beyond a Prescribed Version of Oracle Solaris

/how-to-limit-upgrades-beyond-a-prescribed-version-of-oracle-solaris 2013-11-22T16:02:45+00:00

By default pkg update on Solaris 11 will upgrade your system to the latest versions available on the repository your host is referencing. Many customers don't want this and ask how to prevent the latest from being selected. The answer has always been: don't update your repo or create a custom incorporation package.

Bart Smaalders and Alta Elstad have written this great document telling you how you can do the latter...

The Oracle Solaris 11 Image Packaging System (IPS) provides various methods to control the operating system version to which a server can be upgraded. One method is to provide a custom incorporation package.

An incorporation package specifies the versions of other packages that can be installed. An incorporation package ensures that if you install an incorporate dependency package of that incorporation package, only the prescribed version of the dependent package can be installed. You can create your own custom incorporation package to specify the constraints you want. Using a custom incorporation to control the version of software that can be installed enables you to easily maintain different versions of Oracle Solaris on different machines without maintaining multiple package repositories. Each image can install a different version of the custom upgrade control incorporation package. All systems share the same package repository that contains all versions of software needed by any of the systems.
How to Limit Upgrades Beyond a Prescribed Version of Oracle Solaris (OTN Garage)

Copyright © 2005 - 2016 Colin Seymour All rights reserved. Privacy Policy.
Check out the feed if you do the RSS/Atom thing.