On Wed, Jun 11, 2008 at 10:48 AM, Michael Schuster
<Michael.Schuster at sun.com> wrote:
> All,
>
> (in case this has been discussed before, pls. excuse ...)
>
> a discussion on a Sun-internal alias along the lines of
>
> "do we support compiling on Solaris N+1 and running on Solaris N?"
>
> made me realise that we need to think about this too when publishing(!)
> our stuff; specifically, the KBE packages for SPARC which I recently
> uploaded to bionicmutton were built on Nevada, so they may fail on
> Solaris 10.
>
> Would you agree that while "internal" building and testing is fine and
> necessary both on Nevada and S10, we should probably only put stuff up
> for download that runs on both, ie that's built on S10?

Well, let us consider the situation Blastwave is in.

They comitted to Solaris 8, and thanks to folks there, they are
riding that binary compatiblity guarantee to the 8 EOSL.  And
because of that, a bunch of folks who might do open source
porting for Solaris, don't want to do Blastwave because of personalities
controlling the direction and the mandatory Solaris 8 development
platform (which also means no Studio 12)

The fact remains is that there a fair amount of OSS that has
gotten into SXCE that makes building KDE a lot nicer.  And
there is likely the chance that stuff built on Solaris 10 may
someone conflict with SXCE, and we'll probably have to
see how it works itself out.  There is also stuff not in
os200805 (icu4c for instance) which we do have to build
and shouldn't on S10 or SXCE.  There is also the S10
build using the JDS 2.22 stack, which is also attractive when
you consider that Gnome 2.6 is what, 4 years old now.

I think we are probably better off doing separate distros
for 10, SXCE, and os200805 and making sure the build tools
automatically adjust for OS and architecture so folks
who want to roll their own can do it easily.  I know this
is a little gentoo'ish, but I think in the end, the more
robust the build system is, the more people who are
interested in tweaking their own stuff will be interested.

At some point, the merge with CBE should also not be
constrained to SXCE (which it currently is) so that will
again improve the "standardization" of build platform
for more Open Source for Solaris.

Ben

Reply via email to