Cairo default configuration

[Andrei Tchijov]

Actually it is not "cut and dry".  Just few days ago I was trying to  
build "quartz" versions of Gimp and Dia (I thing Gimp is using Cairo  
and I assume Dia use it too).  With Gimp result was more or less OK.   
There are some quirks but it is usable.  Dia on other hand is  
useless.  I was able to build application, but it has drawing issues  
which renders it completely unacceptable.

At the same time, X11 based version of both programs work just fine.

So if making quartz default option will force maintainers to fix all  
existing problems, then I am all for it. But it is almost guarantied  
to increase number of no-so-happy macport users (at least temporary)  
in the process.

Andrei

On Mar 27, 2009, at 17:18 , Travis Griggs wrote:

> Ryan Schmidt (the maintainer of the Cairo port) asked me to lobby  
> the list for feedback on an issue I recently ran aground of. Cairo  
> can be built with multiple backends. Once upon a time, the default  
> configuration caused only the xlib backend to be built. You had to  
> take extra steps to get the quartz backend built. And then that  
> changed, and BOTH backends were turned on by default. Ryan recently  
> changed it back to the old way, so that quartz requires extra  
> configuration to work. I've lobbied him to revert it (I should take  
> a moment to thank him for providing the port in the first place,  
> thank you very much Ryan) so that quartz is on by default. In fact I  
> might go so far as to say xlib does not need to be turned on unless  
> told to be, but that's because for MY uses, I just need quartz.
>
> --
> Travis Griggs
> Objologist
> I patented thinking... and I still can't find anyone infringing.
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users