How to Serve Multiple Repositories From a Single Location

Many of the steps in this procedure are the same as the steps in the
previous procedure. See the previous procedure for details.

Create a new depot server instance.

Set the path to the repository.

Each pkg/server instance that is managed by a
particular pkg/depot instance must have a unique
pkg/inst_root value.

Check the readonly property for the new
instance.

The default value of the pkg/readonly property is
true. If this value has been changed, reset the value to
true.

$ svcprop -p pkg/readonly pkg/server:studio
true

Set the standalone property for the new
instance.

By default, the value of the pkg/standalone property is
true. Any pkg/server instances whose
pkg/standalone property is set to false
can be served from the same location by a pkg/depot service
instance.

Make sure the value of the pkg/inst_root property is
unique for each instance of pkg/server whose
pkg/standalone property is set to
false.

(Optional) Set the port number for the pkg/depot
instance.

By default, the port number of the
svc:/application/pkg/depot:default service is 80. This port
number can be the same as the port number for any of the
pkg/server instances that will be managed by this
pkg/depot instance. To change the port number, set the
config/port property of
pkg/depot:default.

Restart the pkg/depot instance.

$ svcadm refresh pkg/depot:default
$ svcadm restart pkg/depot:default

Test that the repository server is working.

When users open the http://localhost:80/ location, they
see the http://localhost/solaris repository listed with the
solaris publisher, and they see the
http://localhost/studio repository listed with the
solarisstudio publisher.

If one repository provides packages for multiple publishers, all
publishers are listed. For example, users might see the
http://localhost/solaris repository listed with the
solaris and isvpub publishers.