cairo options in gecko ports

[Jan Beich]

Steve Wills <swills at FreeBSD.org> writes:

> Hi,
>
> Can anyone fill me in on the reasons beyond the options that enable the
> user of the bundled cairo in various gecko@ ports? Why is the option
> there? Is it still needed? I tend to dislike bundling and options that
> aren't needed, so if it's not needed, we could perhaps eliminate it. Any
> objections or reason not to?

Mozilla maintains a fork based on cairo-1.9.5 and only ever runs
regression tests using it. System cairo exposed several issues in the
past from crashes to graphical glitches. r393805 is more recent one.

https://bugzilla.mozilla.org/show_bug.cgi?id=1200934
https://bugzilla.mozilla.org/show_bug.cgi?id=739096

I wonder if Mozilla's fork would work once installed system-wide e.g.,
graphics/mozcairo following suit of graphics/mozjpeg. Cairo upstream
doesn't change API/ABI often[1] and Firefox can still be built with
system cairo. There're probably not many (if any) ports that really need
recent version of cairo.

[1] http://upstream-tracker.org/versions/cairo.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 602 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-gecko/attachments/20151008/cac493e2/attachment.bin>