Bug with multiple port: dependencies in depends_lib ?

[Ryan Schmidt]

On Jul 7, 2008, at 18:44, Ryan Schmidt wrote:

> On Jul 7, 2008, at 16:40, Rainer Müller wrote:
>
>> Daniel J. Luke wrote:
>>
>>>>> Ideally, we should have 1 universal pkg that works on 10.4 and  
>>>>> 10.5
>>>>> intel and ppc.
>>>>
>>>> Yes but no work has been done on this thus far so it can happen
>>>> after MacPorts 1.7.0 is released.
>>
>> What is the important difference between the two? I can only think of
>> the autoconf paths (/usr/bin/svn and /usr/bin/xar are included in
>> Leopard, but not in Tiger).
>
> When built on Leopard, MacPorts sets the x11prefix to /usr/X11. When
> built on Tiger, it sets it to /usr/X11R6. /usr/X11R6 would still work
> on Leopard because Leopard has a symlink at /usr/X11R6 pointing to /
> usr/X11.
>
> When built on Leopard, MacPorts uses the MacOSX10.5.sdk. When built
> on Tiger, it uses the MacOSX10.4u.sdk.
>
> I assume installing the MacPorts port without the +universal variant
> is possible, and that this would give you a non-universal MacPorts.
>
> I would want the MacPorts port to enforce always installing
> universal, and also to use the MacOSX10.3.9.sdk for PowerPC and
> MacOSX10.4u.sdk for Intel. configure, build, install four times (for
> ppc, i386, ppc64 and x86_64), lipo everything together. We can use
> the merge() function that has been committed to trunk to help with
> this. See also the universal variants in openssl and cairo for ideas.

On second thought, I don't see why we want to install MacPorts using  
MacPorts. Doesn't that make it impossible to install MacPorts if you  
do not already have MacPorts?