Renaming a single package is straightforward. IPS provides a mechanism to indicate that a package has been renamed.
To rename a package, publish a new version of the existing package with no content and with the following two actions:
A set action in the following form:
set name=pkg.renamed value=true
A require dependency on the new package.
depend fmri=pkg:/newpkgname@version type=require
A renamed package cannot deliver content other than depend or set actions.
The new package must ensure that it cannot be installed at the same time as the original package before the rename. If both packages are covered by the same incorporation dependency, this restriction is automatic. If not, the new package must contain an optional dependency on the old package at the renamed version. This ensures that the solver will not select both packages, which would fail conflict checking.
A user who installs this renamed package automatically receives the new named package, since it is a dependency of the old version. If a renamed package is not depended upon by any other packages, it is automatically removed from the system. The presence of older software can cause a number of renamed packages to be shown as installed. When that older software is removed, the renamed packages are automatically removed as well.
Packages can be renamed multiple times without issue, though this is not recommended since it can be confusing to users.