You are here

Quick start for oi-userland

Primary tabs

Just writing some ideas from memory for the moment.

Clone the repository from OpenIndiana's Github, it is set as origin:

git clone
cd oi-userland

Add your Github repository as remote:

git remote add my_name

Print for checking:

git remote -v

Initial setup including creation of local on-disk repository and check:

gmake setup
gmake check-environment

If you do not have development tools installed you can install the build-essential package:

sudo pkg install build-essential

Every time you add or modify a component, create a new branch:

git checkout -b my_feature

Keep this branch synchronized with origin/oi/hipster:

git pull --rebase origin oi/hipster

Your local branch is forwarded to the last commit of oi/hipster and your additional commits are kept on top of the stack.

A component consists of several files:

  • Makefile: the recipe to build the software (in the build/$MARCH directory) and install it locally (to the {build/proto directory)
  • patches/: directory containing patches applied before the configuration
  • *.p5m: manifests used to generate the IPS package
  • $(COMPONENT_NAME).license: file containing the licenses applicable to the software

Here is a list of important targets for gmake

  1. clobber: cleans up the component directory completely, including deleting source archives
  2. download: fetches the source archive and verify its SHA256 sum
  3. prep: extract and apply patches
  4. build: configure and build
  5. install: install locally
  6. sample-manifest: generate an IPS manifest based on the files installed locally
  7. pre-publish: generate dependencies and prepare the package but do not publish it
  8. publish: generate dependencies and publish the package to the local repository

First you need to make sure that gmake prep passes, so you can start by changing the component's metadata:

Example with components/libjpeg6-ijg/Makefile:

COMPONENT_NAME=        libjpeg6-ijg
COMPONENT_FMRI=     image/library/libjpeg6-ijg
COMPONENT_CLASSIFICATION=    System/Multimedia Libraries
COMPONENT_SUMMARY=    libjpeg - Independent JPEG Group library version 6b
Variable Value Comment
COMPONENT_NAME libjpeg6-ijg Use the same name as in SFE or other illumos userlands if applicabe, otherwise follow Debian
COMPONENT_VERSION 6.0.2 Should be numerical only, not letters
LIBJPEG_API_VERSION 6b Local variable declared in the Makefile should be prefixed with the component's name
COMPONENT_FMRI image/library/libjpeg6-ijg Follow the convention for the FMRI, check a similar component
COMPONENT_CLASSIFICATION System/Multimedia Libraries This entry should be in the OpenSolaris IPS Classification 2008
COMPONENT_PROJECT_URL Upstream project website
COMPONENT_SUMMARY libjpeg - Independent JPEG Group library version 6b Short description, one-liner
COMPONENT_ARCHIVE_HASH sha256:75c3ec241e9996504fe02a9ed4d12f16b74ade713972f3db9e65ce95cd27e35d To be generated
COMPONENT_ARCHIVE_URL$(LIBJPEG_API_VERSION).tar.gz Full path with archive filename if not equal to COMPONENT_ARCHIVE
COMPONENT_LICENSE IJG,GPLv2.0 Comma separated list of licenses
COMPONENT_LICENSE_FILE $(COMPONENT_NAME).license Omitted if default.

Run the first targets:

  • gmake download: if the checksum fails, replace COMPONENT_ARCHIVE_HASH with the actual hash.
  • gmake unpack: once the sources are extracted, concatenate the license files to $(COMPONENT_NAME).license, here "libjpeg6-ijg.license".
  • gmake patch: to apply patches.

If you do not have any patches, you can as well run gmake prep directly which does all these three steps.

NOTE: if you update a component without modifying the Makefile (for instance if you only fix the manifest) then you need to update the COMPONENT_REVISION variable in the Makefile to trigger a rebuild of the component on the build server. This variable is set to zero by default, so if it is not in the Makefile already, add:


just under COMPONENT_VERSION, otherwise just increment its value.

Patch, Build and install

If you starta new component you can copy a template Makefile from the templates directory: choose the file corresponding to the software's build system.

The included .mk file providing build/install rules depends on the build system, example:

include $(WS_TOP)/make-rules/

Look in the make-rules directory for more

File Build tool Ant AT&T package tools CMake Autotools Ruby GEM plain Makefile Perl Python distutils

Read the .mk file to see which variables you can modify, in general you can find variables such as:

  • *_ENV

For example, you may add this line for an Autotools-based component:

CONFIGURE_OPTIONS+= --enable-shared

It is now up to you to: patch, play with the configuration flags and such... Do not hesitate to look around to see how it is done in other components !

Prepare the IPS manifest

When the install target passes, you can run:

gmake sample-manifest

to generate a manifest from the list of installed files.

Copy the file build/manifest-generated.p5m to $(COMPONENT_NAME).p5m and edit it:

  • Add you name as contributor
  • Remove unused entries from the manifest:
    • directories: :%g/^dir/d (Vim)
    • static libs: :%g/\.a$/d (Vim)
    • libtool files:: :%g/\.la$/d (Vim)
    • Python *.pyc: :%g/\.pyc$/d (Vim)

For some components, specific rules need to be applied: they can be implemented with *transforms* or individually with directives. Some example can be found in the transforms directory at the root directory of oi-userland.

Add packages requirements

When you are statisfied with the package you can generate runtime dependencies:


This will add a list of detected dependencies at the end of the Makefile.

If there are build dependencies which are not detected, they should be added manually!

If the Makefile provides REQUIRED_PACKAGES, dependencies can be installed automatically with:

gmake env-prep

Publish the package

Run gmake publish: if the dependencies are resolved and the manifest is valid, your package is published to the local repository. You can then install your package locally and test it.

To be able to search for the new packages in the local repository you need to rebuild search indexes:

pkgrepo refresh -s /path/to/my_repo

You can even rebuild the entire metadata:

pkgrepo rebuild -s /path/to/my_repo

Submit your component

Run gmake clobber then gmake publish to check that the component is publishing correctly.

If it is the case, you can cleanup your branch then submit a pull-request.

First you need to *squash* all your commits into one, check how many commits are to be considered:

git log


git rebase -i HEAD~N

with N the number of commits to be squashed, and follow the instructions: the letter 's' should be put in place of 'pick' for the N - 1 commits before the last.

If you made a mistake with the commit message or author, use:

git commit --amend

with the relevant option.

Then you are ready to push:

git push my_name my_feature


git push -f my_name my_feature

if the branch you just rebased had already been pushed: since the history is rewritten you need to force the push, be careful.

Go to your Github profile and open a pull request.