On Tue, Mar 27, 2012 at 11:42:12PM +0100, Andrew Benton wrote: > I can see 3 options: > 1) We give up on --enable-system-cairo and statically compile their > version of Cairo into Firefox. (We decided to do a similar thing with > Mplayer and FFmpeg) > 2) We patch Firefox to revert the change (it's a tiny 2 line patch > https://bugzilla.mozilla.org/attachment.cgi?id=595000 ) > 3) We patch Cairo to add the mozilla code into the system Cairo > https://bugzilla.mozilla.org/attachment.cgi?id=609898
My preference would be to go with option 2, since it's apparently a windoze bug ;-) No, seriously, as much as I hate being dictated to by mozilla devs, option 3 is the only realistic way to go. At one time, I dropped the apng patch from my own builds because, contrary to my previous expectations, everyone else was ignoring it because the png devs had rejected it. And then I saw a report (unconfirmed) that mozilla had been *very* slow to fix a png vulnerability in their internal copy of the code. Using system versions of libraries is always a better way to go. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
