Ken Mays wrote:
> On Fri, 2008-01-04 at 21:48 -0800, Garrett D'Amore wrote:
>
>> PS: Last time I tried, any of the blastwave packages that brought in GTK
>> font support were very, very toxic on OpenSolaris. To the point that the
>> only way to get back to a working desktop was to reinstall from scratch.
>> I strongly discourage the use of blastwave on OpenSolaris... as long as
>> the packages it has are built on Solaris 8 there are going to be issues
>> with some of the "layered" software, such as most GUI apps.
>>
>
> Both Blastwave's CSWkde 3.4.3 and CSW GNOME 2.16.3 worked fine on SXCE b68
> when installed on a Sun Blade 100. I've use them in combination with JDS and
> CDE without ANY issues in a full production environment with heavy OpenGL
> graphic workloads.
>
> As Garrett mentioned though, you are looking at binaries built on Solaris 8.
> I've ran both desktops on my Sun Blade 100 for months on SXCE configs - and
> having a sys admin in Germany running a 80-user setup which ran very stable
> for months. I won't say **all** packages work fine as you use SXCE/SXDE or
> the other OpenSolaris distros. Also, several people from Sun (ahem!) are
> using Blastwave's KDE and GNOME packages (as well as those nice Mac laptops).
>
I suspect using a full installation of blastwave's Gnome would work.
But trying to download one GTK application (e.g. mplayer) and use it,
has proved to be completely toxic to the Solaris-provided Gnome/JDS
environment.
I've tried this on numerous installations of Nevada, across several
builds (going back perhaps as far as b64), and each time I try it, I've
immediately regretted it. And found that I could not not undo the
damage -- I think the problem is incompatibilities in fonts or font
libraries, but I've not tried to isolate it further.
-- Garrett
