[29988] trunk/dports/graphics/cairo/Portfile

[Yves de Champlain]

Le 07-10-18 à 14:08, Ryan Schmidt a écrit :

> On Oct 17, 2007, at 07:54, source_changes at macosforge.org wrote:
>
>> Revision: 29988
>>           http://trac.macosforge.org/projects/macports/changeset/ 
>> 29988
>> Author:   yves at macports.org
>> Date:     2007-10-17 05:54:20 -0700 (Wed, 17 Oct 2007)
>>
>> Log Message:
>> -----------
>> Add PDF backend variant
>>
>> Modified Paths:
>> --------------
>>     trunk/dports/graphics/cairo/Portfile
>>
>> Modified: trunk/dports/graphics/cairo/Portfile
>> ===================================================================
>> --- trunk/dports/graphics/cairo/Portfile	2007-10-17 12:46:29 UTC  
>> (rev 29987)
>> +++ trunk/dports/graphics/cairo/Portfile	2007-10-17 12:54:20 UTC  
>> (rev 29988)
>> @@ -52,6 +52,9 @@
>>  	configure.args-append \
>>  		--disable-xlib
>>  }
>> +variant pdf description "Enable PDF backend" {
>> +	configure.args-append --enable-pdf
>> +}
>
> So, what's this?
>
> I didn't even know cairo had an --enable-pdf switch. I only use  
> cairo for graphviz, and one of the features graphviz gains by using  
> cairo is the ability to output pdfs. This has always worked for me,  
> though I've never used --enable-pdf. So does --enable-pdf get us  
> anything extra? I see from ./configure --help that the default for  
> this option is "auto" so maybe for me it was automatically on and  
> for you it was automatically off? I wonder what influences this  
> automation. Does the pdf ability need any additional dependencies?  
> If not, shouldn't we enable pdf all the time rather than putting it  
> in a variant?

There are no dependencies apart from those already listed but I don't  
how the "auto" is worked out.  I put it as a variant mostly because I  
was not sure what effects it could have, but it was not necessarily  
the best approach.

yves