Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

There are multiple sources for add on packages for Solaris, blastwave, openCSW, Sunfreeware, and pkgsrc. Ideally, I'd like to stick as close as possible to a single packaging system, so which of these would you recommend I use? Or, should I ignore them, and roll my own?

share|improve this question

3 Answers 3

OpenCSW has the most up to date packages of the three sites, unless you specifically want the full GNOME desktop stuff. We have all the gtk/etc basic libs up to date, and even firefox3. It's just that no-one so far has cared enough about the gnome desktop environment to update "the desktop".

Check out the packages page, for revs of what we have.

http://www.opencsw.org/packages

share|improve this answer
    
For those who like tinkering with packages: It's also easy to use build descriptions from OpenCSW: svn co --ignore-externals gar.svn.sourceforge.net/svnroot/gar/csw/mgar opencsw The OpenCSW build system abstracts away most of the annoyances of Solaris package building. –  automatthias Feb 21 '10 at 12:58

I think Sunfreeware is seen as the most stable and reliable source, although it often lags behind Blastwave with regards to recent versions.

In my shop, we employ Sunfreeware for our production packages, and Blastwave for development tools. This has the nice benefit that there is a physical and logical distinction between the two sets of packages, as Sunfreeware install under /usr/local and Blastwave installs under /opt/csw.

Hence, when we build and link software against /usr/local on our development machine, we are confidant that it closely replicates our production environment, whereas everything under /opt/csw is considered a kind of free zone, where all kinds of development packages and their dependencies are installed.

Blastwave also has a recent build of Trac - which is a blessing because building that from source on Solaris is painful.

PS: And no, you certainly should NOT ignore them, not only do they save huge amounts of time, they also have also been built by experts who know how to iron out various incompatibilities and issues that may exist. Dont be afraid to build your own either if there is good reason - you can often drastically cut down on dependencies by building 'lite' versions of packages (e.g. I build a version of PHP that excludes all XML related funcitonality). Ultimately you need to find a balance that suits your needs and environment.

share|improve this answer

If you're coming from an environment like Ubuntu or Debian where 99% of the time you're one apt-get away from whatever package you want to install, then Blastwave is going to be a better fit. It comes with a tool that overlays pkg-add called pkg-get that will take a package name, find it in the the network repository and install it.

On our Solaris Express machines, we use Blastwave almost exclusively. It's fast, easy and we haven't had any reliability issues with the packages (we run a 24/7 messaging service). Occasionally, there is a package Blastwave doesn't have, and we'll manually install that from Sunfreeware if its available or build from source.

Alternately, if you're just getting started with Solaris, giving Opensolaris a shot is also an option. Similar, apt-get like experience for all packages (including system ones). The repos are not quite as large as Blastwave yet but getting there. We've migrated about 80% of our Solaris Express boxes over to Opensolaris 2008.11 and 2009.06.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.