SFE - Software Packages for Solaris, OpenIndiana and OmniOS

(seriously, do *not* mirror these repositories - instead help me build a release repo which is HA and can be mirrored)

Browse

By clicking on the URL you can browse available packages for your OS:
(X86 only! Donate a SPARC build zone? Well there is something in preparation, ask for updates on this!)

Solaris 11 IPS Packages Repository (517)
http://sfe.opencsw.org/localhosts11

Solaris 12 (internal) IPS Packages Repository (291)
http://sfe.opencsw.org/localhosts12OpenIndiana OI151a8 (and a9) IPS Packages Respository (333)
http://sfe.opencsw.org/localhostoi151a8

OmniOS IPS Packages Repository (192)
http://sfe.opencsw.org/localhostomnios

OpenIndiana Hipster (moving target) IPS Packages Repository (234)
http://sfe.opencsw.org/localhostoih

discontinued: testing repo localhosts12nogccdeps -> please use localhosts12 now.

Publisher

To configure those repos as publishers use: (pick only the one matching you OS)
pfexec pkg set-publisher -G '*' -g http://sfe.opencsw.org/localhosts11 localhosts11  #S11
pfexec pkg set-publisher -G '*' -g http://sfe.opencsw.org/localhosts12 localhosts12  #S12
pfexec pkg set-publisher -G '*' -g http://sfe.opencsw.org/localhostoi151a8 localhostoi151a8  #old OpenIndiana
pfexec pkg set-publisher -G '*' -g http://sfe.opencsw.org/localhostomnios localhostomnios  #OmniOS
pfexec pkg set-publisher -G '*' -g http://sfe.opencsw.org/localhostoih localhostoih  #new OpenIndiana Hipster

These repositories are 1:1 copies from the build machines, so please expect contents to change frequently and as well, the content may have bugs. Drop me a note (in the comments, or by email) if a package works (yeah, we like that!) or breaks for you (we need to know that).
One day there will be a process which establishes a voting system. It should be used to promote packages from the development repositories to a public release repository. If you have ideas, how a test / promotion process should look like, please let me know (in the comments or by email).
If you are a programmer who can create or at least design a web workflow for the package promotion, then please get in contact very soon to discuss possibilities.
What we need as well for SFE are volunteers for testing the packages. Would you like to be one?
 

What is it good for

These are development repositories but good for normal use.
For production use, you can compile packages yourself, or, help us building up a "release" repository with QA and a voting website to get packages promoted to "release".

Mirroring the Repository?

Please do *not* mirror these development repositories. You can download the package and prerequisite packages with special switch "-r" to the pkgrecv command. That saves capacities on the server. I'm sure you understand that mirroring 18Gbytes for the whole repository is not the right thing to do.
Once a release repository exists, you are welcome to mirror this (though we understand that it only makes sense in very, very rare cases).
Thank you!

Notes

Please keep in mind: You can install any exact package version if you specify the *complete* FMRI listed including the timestamp.
Example:
pkg list -avf postfix
[...]
pkg://localhosts11/sfe/service/network/smtp/postfix@3.0.3,5.11-0.0.175.3.1.0.5.0:20160108T10293
[...]
To install exaclty that version and no other, use:
pfexec pkg install -v pkg://localhosts11/sfe/service/network/smtp/postfix@3.0.3,5.11-0.0.175.3.1.0.5.0:20160108T10293

This way, you could install exactly an *older* or a *newer* package then the resolver would auto-select for you. This enables you to help yourself, in case we have a broken package in these build repositories. You simply install another version which is working for you.

Questions?

Drop me an email at sfepackages at g mail dot com - or create a useraccount here on the blog and leave me a comment.
Need additonal packages? Put them on the package wishlist here http://sfe.opencsw.org/wishlist!