Ian Collins wrote:
Stefan Teleman 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 ?
Would it be possible to base your KDE build on Blastwave libraries? As
the most actively maintained set for Solaris, I can see them moving
towards becoming de facto standards.
If this were to happen, I think you KDE would become more popular.
Glynn, could the same be done with JDS?
Ian
If you're talking about Nevada JDS, then no, Nevada packages have to be
based on other Nevada packages.
Of course a _non_ Nevada JDS project could do whatever it wants...
In addition, as of Oct 28 (the date of the JDS source + build
environment release) there's nothing standing in the way of a movement
to somehow synchronize Blastwave and Nevada JDS libraries (except a lot
of motivation and a lot of hard work by a lot of Sun and non-Sun people).
Which, I think (as I keep squawking about on my blog) would be
absolutely great.
Eric
_______________________________________________
opensolaris-discuss mailing list
[email protected]
