Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Option 1: Installing software from OpenIndiana repositories via IPS

OpenIndiana uses the Image Packaging System - IPS, pkg(5) , the same package management system as Oracle Solaris 11.
Oracle is continuing practice of providing well written manuals:

To find more information on IPS/ pkg(5), using man command, use:

Code Block
$ man -s 5 pkg

The command line package manager command is 'pkg'.
To find more information about pkg(1) , using man command, use:

Code Block
$ man pkg

In IPS parlance, we are talking about adding publishers in place of term repositories.
Package management is performed using accounts with elevated Role Based Access Control (RBAC) privileges (using pfexec or sudo before commands shown below).

Adding publisher

Code Block
$ pfexec bash
# pkg set-publisher -g repository_url repository_name

Replacing publisher

Code Block
# pkg set-publisher -G old_repository_url -g new_repository_url repository_name

Replacing publisher - example

Code Block
# pkg set-publisher \
-G \

Listing publishers configured on the local system:

Code Block
# pkg publisher
PUBLISHER                   TYPE     STATUS P LOCATION             origin   online F
hipster-encumbered          origin   online F

'OpenIndiana hipster' repositories (as of February, 2017)

openindiana.org primary package repository
hipster-encumbered encumbered license packages
localhostoih party Spec Files Extra (SFE) packages

Syntax for searching remotely for IPS packages

Code Block
# pkg search -rp package_name

Syntax for installing an IPS package

Code Block
# pkg install package_name

Syntax for upgrading a package

Code Block
# pkg update package_name

Upgrading all the packages on the system, with linked image Solaris Zones. (-r) and verbose output (-v)

Code Block
# pkg update -v -r

Option pkg -r updates all Solaris Zones , if not issued, thay are kept unupdated untill -r command is issued on update or they are updated separately.


Option 2:  Install software from SmartOS repositories via pkgin

All illumos-based operating systems, like OmniOS, Openindiana and SmartOS can use the repository from Joyent/SmartOS. Its main advantage is that you find there a lot of very up to date packages.

A list of available software: in folder  (or

If you want to install software via pkgin (installs every package to /opt), you need to (console as root):

  1. add /opt/local/{s,}bin where all software is installed to your PATH (in your shell, maybe save to your .profile):

    Code Block
    export PATH
  2. install the bootstrap-loader: (use the loader according to your repository, see

    Code Block
    :; curl | gtar -zxpf - -C /  
  3. update the repository database:

    Code Block
    :; pkgin -y update
  4. install the needed package, for example – Apache 2.4.6:

    Code Block
    :; pkgin -y install apache-2.4.6 

    or, just for newest 2.4:

    Code Block
    :; pkgin -y install apache-2.4

For more information see:

Option 3: Compile yourself

You need a compiler like gcc; download the sources, switch to the folder with your sources (make the content of your 'sourcefolder' executable recursively) and compile via:

Code Block
:; cd /sourcefolder
:; ./configure
:; make
:; make install

You might want to first look into ./configure --help to see what options are available for building the software – quite often, some features useful for you might notbe a general choice enabled by default, or might require other dependency software to be available first in binary or source form, in order to compile.

For building software from NetBSD pkgsrc from sources, see page: pkgsrc in OI .

Option 4: Build software using oi-userland

For contributing to oi-userland, see page: Building with oi-userland