Comment 126 for bug 512615

Alexander Sack wrote:
> On Sun, Feb 07, 2010 at 03:55:29PM -0000, Yuri Khan wrote:
>> Alexander Sack wrote on 2010-02-04:
>>> This has highest priority ... but we prefer this getting fixed
>>> upstream rather than running our own patches or even system cairo
>>> again
>> What are the negative consequences of building with system cairo?
>>
>
>
> major potential issues with security updates ... up to the points
> where we need to revert from system to non-system cairo in a security
> update ... hence we must keep this visible and fix for real or get
> mozilla to not bump cairo requirements in security updates.

I guess I don't really understand what you expect to happen between now
and beta1. The chances of an lcd filtering patch landing in cairo
master in this timeframe is minuscule and even if it did, there'd be
hardly enough time for testing. So we're limited to the patch that is
out there right now. I only see four options:

(1) --enable-system-cairo
(2) Get someone from mozilla to ack the patch that we've been shipping
in cairo for ages
(3) Take a page out of debian's book, apply the patch and just don't
call the browser firefox. This needs to be an option, otherwise we have
no leverage for (2). Or ship two versions of the browser, one that is
called firefox and looks like shit, and one that is called namoroka and
looks good.
(4) Do nothing, repeat the disaster that is bug #217908 and let people
deal with it in PPAs.

Whatever solution is adopted, it's better make the decision now than in
six weeks, in order to maximize testing exposure. Nothing is really
going to change between now and then.