30 Dec
2011
30 Dec
'11
9:45 p.m.
On 30 December 2011 16:34, Timothy Pearson <kb9vqf(a)pearsoncomputing.net>wrote;wrote:
ok understood
On 30 December
2011 16:11, Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>wrote;wrote:
How dependent is kicker on libart? It might be easier to just recreate
the
>
http://bugs.trinitydesktop.org/bugzilla/show_bug.cgi?id=554
I never have seen any crash like those described. Then again,
Slackware
has libart 2.3.20 installed. I wonder whether
these libart crashes are
Debian related only because of the old version? I see the point of
maintaining the package now, but I wonder whether version 2.3.20 has
all
of the alleged missing patches.
The crashes seem to be happening on certain hardware only. For example
I
have not seen them myself on server-grade hardware, but others with
comparable desktop hardware have had kicker crash.
There is inherent instability in libart, and it is possible that even if
you don't see the crash that some of your users might in the future.
Tim
few functions used by kicker and libart, sort of
absorbing it into
kicker.
I'd rather have a few extra drawing ops then
maintaining another library.
Any thoughts?
The library is small and we would probably end up putting just as much
effort into rewriting those parts of kicker to be honest.
Unless someone here is REALLY good with vector graphics and the mechanics
of making things work properly when they are rasterized keeping libart is
the easiest/safest thing to do.
Tim