Some things Oracle just doesn’t get

Yesterday at the NLUUG conference I picked up a Solaris 11 Express CD in a nice brownish CD sleeve (I say "nice" because it feels and looks different from the generic white sleeves). Here’s a scan of the back of the sleeve, with a big sticker over the flap (click on image for a larger, readable version).

scan of cd sleeve

I thought shrink-wrap licenses went out with Disco, or something like that?

A little searching gets me to the license text so I can read it before opening the package to get at the license itself. The one saving grace is that the license condition is "opening this sealed software package and using the software" (emphasis mine) so it’s not classic shrink-wrap.

In classic fashion, though, I can’t give away this CD to someone else, not even if they want to use it to develop or demonstrate an application on Oracle Solaris.

If we turn to the license text itself, the section on "Open Source Software" rubs me in every possible wrong way, starting from the definition

"Open Source" software – software available without charge for use, modification and distribution – is often licensed under terms that require the user to make the user’s modifications to the Open Source software or any software that the user ‘combines’ with the Open Source software freely available in source code form.

It’s increasingly difficult to engage with Oracle Solaris except as a commercial entity; increasingly difficult to easily check if the software you produce (you in the sense of "a Free Software community") might work on that OS. Combine that with a compiler that’s also increasingly hard to get and, well .. it certainly seems like there’s no interest in third-party software development except on a commercial basis.

We’ve been keeping Qt on Solaris (with Sun Studio) going for three years now. That has led to many patches in the compiler, many in WebKit, and most of the time we’ve got a good working relationship with upstream (i.e. Nokia / QDF). I still think we can deliver a Qt suitable for other applications’ use (maybe not VirtualBox, but that’s still dreamable). Now the Qt modules maturity list shows that Solaris (along with the proprietary UNIXes that still exist; remember at some point Solaris distinguished itself from those by being reasonably-almost-open) is "done". Needs new maintainer. That bodes ill from an upstream-support perspective.

Note about the compiler: you can’t get patches (beyond the released 12.2 version) without a support contract, as far as I can tell. So there’s no easy way to get a version of Sun’s C++ compiler that has all of the bug fixes prompted by the KDE4-Solaris project. The partly-patched version I still have on my Solaris machines is falling behind, so that I can’t even compile all the stuff I’m trying to package. This is one of the reasons the KDE4-Solaris project is looking hard at both gcc and Pathscale.

This entry was posted in KDE, OpenSolaris and tagged , . Bookmark the permalink.

6 Responses to Some things Oracle just doesn’t get

  1. Cláudio says:

    A bit off topic and obviously oblivious to the details but I just wonder what happens if you open the package and someone else uses the software?

    • adridg says:

      @claudio: presumably there’s still also a EULA to go through when installing / using the software, which has only a use condition.

  2. anon ymous says:

    How about clang? clang/llvm 2.9 can now build Qt with Webkit.

    • adridg says:

      @anon: but then i’d need to port clang / llvm to solaris first.

      • anon ymous says:

        clang/llvm bootstrapped with gcc 4.x works out-of-the box on Solaris Express 11, there is even a specfile in SFE.

  3. Pingback: Links 15/5/2011: GNU/Linux in Munich and Fire Stations | Techrights