Dick Hoogendijk wrote:
> On Mon, 14 Jan 2008 09:47:34 -0800
> "Garrett D'Amore" <garrett at damore.org> wrote:
>> 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.
>
> Still, this is very weird. The Blastwave packages are completely
> isolated. If you make sure /opt/csw/bin is not in your path I can see
> noway a packages like mplayer can pollute the JDS environment.
I've heard of people having problems with the blastwave libfontconfig/fc-cache
writing cache files incompatible with the system libfontconfig/fc-cache, and
don't believe those are isolated or kept in a blastwave-specific directory at
all. I've never had time to investigate though.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
