gimp2 +no_x11 needing +quartz

[Michael Gersten]

On Apr 16, 2010, at 6:39 AM, Ryan Schmidt wrote:

>
> On Apr 14, 2010, at 00:25, Michael_google gmail_Gersten wrote:
>
>>> gimp2 @2.6.8_0+darwin_9+no_x11+quartz (active)
>>
>> That "+quartz" actually came as a surprise. I tried
>>
>> sudo port -f install  gimp2 +no_x11
>
> You probably don't want to be in the habit of using "-f".

Probably not, but until +universal on install gets here, ... :-)

(Yea, I've picked up a bad habit.)

>> And it got as far as
>>
>> Applying patches to gtk2
>> --->  Configuring gtk2
>> Error: Target org.macports.configure returned: cairo must be built
>> with the +quartz variant enabled.
>>
>> Kleiman-ibook:~ michael$ port installed cairo
>> The following ports are currently installed:
>> cairo @1.8.10_0+macosx+no_x11 (active)
>>
>> So why does gimp2, +no_x11, not force the +quartz flag to its
>> dependencies? Are end users supposed to track what dependencies
>> require what additional dependencies?
>
> If cairo was not already installed, I believe it should have been  
> installed with the +quartz variant, because you were installing gtk2  
> with the +quartz variant. But if you already had cairo installed  
> without the +quartz variant, the only thing the gtk2 port can do is  
> detect this and tell you to fix it. A port cannot cause a dependency  
> to be installed with a particular variant. That's ticket #126.  
> Though dependencies that haven't yet been built will inherit the  
> variants requested on the command line.

In the past, trying to install stuff with +universal without the -f  
would fail if a dependent did not have +universal; adding -f made it  
work and forced a redo of whatever did not have matching variants.

Here, my thoughts were the same -- by passing -f to port install, I  
wanted any existing dependencies to be changed to match.

So why does it work with +universal and not with +no_x11?

(This was the only place I had to go and add +quartz. Everything else  
compiled just fine.)