omnios-wiki

OmniOS Wiki

View the Project on GitHub

Note: These pages have been imported from the OmniTI wiki and are in the process of being converted.
Information here may not yet be correct for the Community Edition.

Populating IPS Repos

So we have set up a fancy IPS repo, but now we need to get packages into and out of it. We could either copy all the packages or only some of them. In either case, the source and destination URIs may be any combination of http:// and file:// URIs.

Wholesale Repo Copy

# pkgrecv -s https://pkg.omniosce.org/r151022/core/ -d file:///repo/myomnios/ 'pkg:/*'

What we have done above is tell pkgrecv to suck down all the packages from pkg.omniti.com/omnios/release and push them into a local file-based repo. The pkg:/ at the end is just saying get everything.

Cherry-picking

You could just put in a pattern to match if you wanted specific packages.

pkgrecv -s https://pkg.omniosce.org/r151022/core/ -d file:///repo/myomnios/ pkg:/terminal/screen pkg:/shell/zsh

Specify as many pkg: FMRIs as needed (you can use shell-style globbing as in the wholesale example above.)

Changing Package Metadata

To pull down an individual package for editing, do something similar to the following example. You may want to make a metadata change, such as fixing a missing dependency, correcting a typo in the summary, or changing the publisher name. The gist is that you pull down a copy of the package to your local filesystem, make your changes, then publish an updated package back to the original repo or maybe to a different repo.

Changing package metadata in this way will result in a new package with a different timestamp from the source package.

Make a working directory somewhere:

$ mkdir /home/me/custom

Pull down a copy of the package to this directory. Using --raw gets us the package metadata as well as the content, and treats the destination as a plain directory and not a repository

$ pkgrecv -s file:///repo/myomnios -d /home/me/custom --raw pkg:/system/pciutils/pci.ids

In your specified directory you’ll end up with a subdirectory structure of package-name/version-string, e.g

./system%2Fpciutils%2Fpci.ids
./system%2Fpciutils%2Fpci.ids/2.2.20120906%2C5.11-0.151002%3A20120907T175614Z

Optionally make metadata changes. In the version directory there is a file, manifest. Make any necessary changes in this file.

Use pkgsend to publish the package to a repo:

$ cd system%2Fpciutils%2Fpci.ids/2.2.20120906%2C5.11-0.151002%3A20120907T175614Z

$ export PKG_TRANS_ID=$(pkgsend -s file:///repo/myomnios open -n system/pciutils/pci.ids@2.2.20120906,5.11-0.151002)

$ pkgsend -s file:///repo/myomnios include manifest

$ pkgsend -s file:///repo/myomnios close
PUBLISHED
pkg://omnios/system/pciutils/pci.ids@2.2.20120906,5.11-0.151002:20120907T180039Z

Note that when opening a new repo transaction, the environment variable PKG_TRANS_ID gets set by capturing the output of the pkgsend open operation, which returns a unique identifier for that transaction. PKG_TRANS_ID must be set for the subsequent actions to succeed.

Notice as well that I didn’t include the timestamp portion of the existing package’s FMRI. It’s not needed; as you can see, the updated package gets a new timestamp that corresponds to the publication date.