The system that hosts the IPS package repository can be either an x86-based or a SPARC-based system.
A system that hosts an IPS package repository must be running at least Oracle Solaris 11 11/11. Newer versions of Oracle Solaris 11 provide additional repository creation and maintenance features, in addition to other new Oracle Solaris features and security fixes.
The pkgrepo verify and pkgrepo fix commands are available only with Oracle Solaris 11.1.7 and later.
The pkgrepo contents and pkgrepo remove-publisher commands are available only with Oracle Solaris 11.2 and later.
The pkgrecv -m all-timestamps behavior is the default with Oracle Solaris 11.2 and later.
The pkgrecv --clone option is available only with Oracle Solaris 11.2 and later.
The svc:/application/pkg/mirror SMF service is available only with Oracle Solaris 11.2 and later.
The scalable repository server, pkg.depotd, and the pkg.depot-config command are available only with Oracle Solaris 11.2 and later.
The pkgrepo verify command includes dependency checking in Oracle Solaris 11.4.
The amount of disk space required depends on how complete your repository is. See Comparing Repository Content Sources.
The repository file for the release creates a 9.5GB repository.
Copying the Oracle Solaris support repository creates a 95GB repository.
Because best practice is to keep local repositories updated with all SRUs since the last Oracle Solaris dot release that you added, plan to use 10-15 GB of additional space each year for SRUs.
Additional software, such as Oracle Solaris Studio or Oracle Solaris Cluster, requires additional space in the package repository.
If one system hosts more than one IPS repository, make each repository a separate ZFS file system so that you can rollback and recover each repository separately.