[EMAIL PROTECTED] wrote:
On 12/20/05, Glynn Foster <[EMAIL PROTECTED]> wrote:
Having BOTH means giving users (actual and potential) a choice.
It's really about resources issues. The desktop team within Sun is
already swamped enough without having to look and fix issues with KDE as
well. But yeah, I completely agree with you - having the ability for
customers to install KDE off the companion CD or off some online package
repository would be *ABSOLUTELY FANTASTIC*.
is Sun willing to at least give access to a SVN repository so the KDE
Solaris port source code and the associated required libraries source
code (which, by the way, are three times the size of what used to be
the Companion CD) have a material presence at OpenSolaris, where
people can actually collaborate and do work ?
if that is not possible, then the current situation will not change,
and will not improve. KDE can be downloaded right now off the 'Net, in
its various shapes, forms and incarnations.
having a real, collaborative engineering effort at OpenSolaris does
not formally imply product support from Sun.
--Stefan
Hi Stefan,
First, congratulations on the KDE 3.4.3 release!
To go along with Glynn's reply, here's a good analogy I think.
Suppose we were talking about Python and you were a Python porting
Solaris expert instead of a KDE one.
By virtue of being part of JDS now, the port source code for Sun's
Python is open and accessible on opensolaris.org. As a result, it is now
possible for non-Sun Solaris developers like you to help co-development
Python for Nevada (aka Solaris next) -- and even Solaris 10 via an
update release if deemed necessary.
Back to KDE. Per the OpenSolaris roadmap[1], the same thing will
eventually happen with KDE via the Companion CD. Which is to say, Sun's
port source code and development environment for the Nevada KDE packages
will be launched on opensolaris.org sometime in Q1 '06.
Of course it'll be harder than Python because KDE/QT is a _whole lot_
more complex.
The good news is it'll be easier in a big way too: Developers of
Companion CD packages have _far_ fewer constraints than developers of
real Nevada packages (like Python) since CCD packages are unsupported
and live in /opt.
Eric
[1]: http://opensolaris.org/os/about/roadmap/
_______________________________________________
opensolaris-discuss mailing list
[email protected]
