Stefan Teleman wrote:
On 12/21/05, Ian Collins <[EMAIL PROTECTED]> wrote:
This would be a start in cleaning what appears to an outsider to be the
messy situation of conflicting version of the same application. Then
you wouldn't have to spend your time keeping the KDE dependencies up to
date. Freedom can also be freedom for the drudgery of maintaining thins
you require, rather than those you want to build and grow. I know, I've
been there.
There is nothing i would like more than for all of us involved in this
to finally agree on a set of standards, and follow them. That means
*all* of us. I have asked this very exact question 6 months ago, on
this forum.
What was the response ? Does anyone remember ? If my recollections are
correct, of all the parties of whom the question was asked, only two
answered. one of them was OpenSolaris (a.k.a. Glen), the other one was
solaris.kde.org. (a.k.a. yours truly).
Blastwave chose to stay silent.
--Stefan
To me, the most important bits are these:
1) compiled for the OS build I want to run on to avoid duplicate libs.
2) compiled with modern CPU support (eg SSE2, SSE3, etc).
3) compiled with all X extensions that OS revs supports
4) Source packages (as compiled) and build infrastructure available
so that binary bits can be replicated.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[EMAIL PROTECTED] http://blogs.sun.com/barts
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
