package repository

Search Packages

Advanced Search

Browse Packages

The list of all available packages can be found here.

About

PACKAGES/SOFTWARE CONTAINED IN THIS REPOSITORY ARE PROVIDED AS IS AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

These packages are free, but note, that the contained software may not allow you to redistribute or modify it as you want. Obey its license terms! Usually such terms are part of the software"s documentation or it provides a command, which displays such information. Last but not least pkg info $pkgname may show you the URLs, where one may find more information about the software and possible license options.

The basic idea behind the packages is, to provide more or less recent software, better optimized and relocatable packages, which use as much as possible of the original OS software and thus reduce the maintenance overhead on our side as much as possible. So basically re-use instead of re-invent the wheel.

Packages are updated on demand and without any notice. Packages older than 14 days have usually production quality, i.e. they are used on our servers and/or desktops (but remember, our definition of "ready for production" might be different from yours!). Everything else should be seen as "work in progress"/experimental. Have a look at the timestamp (see the blue part below) to determine the age of a package.

The version string of our packages has the following format: ${SW_VERSION},${OS_REL}-${PKG_REL}${SRU}[${PKG_MIN}] (e.g. texlive−all@1.0.20150521,5.11-1.2.13.6:20151007T193407Z) with the following meaning:

${SW_VERSION}

This is per default the version of the software delivered by the package. Usually it is a number tripple: {Major}[.Minor[.Patch]...] - see also Semantic Versioning. If a software does not follow these rules, we try to use a schema, which lets one still deduce the "real" version of the software.

${OS_REL}

This is the major release of the OS on which the package has been built, on Solaris/Ilumos usually the output of uname -r, i.e. something like 5.11 or 5.12

${PKG_REL}

This number indirectly represents the build script version/environment used to build the software. It starts with 1 for each new ${SW_VERSION} and than gets simply incremented if needed (i.e. sources did not change, but something related with the built process).

${SRU}

This part has the format A.B.C, where A represents the minor release and B.C the SRU version of the OS on which the package has been built. So e.g. for Solaris 11.3 SRU 9.4 we would use 3.9.4.

${PKG_MIN}

This part is used only, if a new package version is needed but neither the sources nor the built script version/environment has changed. E.g. the Ubuntu PPA stuff is pretty fragile and may fail to build a package or simply doesn't accept one for obscure reasons. In this case one needs to upload all the stuff again, but it than gets accepted only, if the version number has been changed. If this happens, this part gets used/incremented.