[43132] trunk/dports/x11/xorg-libAppleWM/Portfile

[Jeremy Huddleston]

On Dec 5, 2008, at 14:29, Ryan Schmidt wrote:

> On Dec 5, 2008, at 16:09, Jeremy Huddleston wrote:
>
>> On Dec 5, 2008, at 13:44, Ryan Schmidt wrote:
>>
>>> If you're going to run autoreconf, you need to declare a build  
>>> dependency on the port that provides autoreconf...
>>> That would be the autoconf port. Probably declaring a build  
>>> dependency on all three (autoconf, automake, libtool) is required.
>>
>> That's what that port:libtool dependency is for.  libtool depends  
>> on automake which depends on autoconf.  I didn't realize I needed  
>> to explicitly require all three. I'll update that.
>
> libtool only has a build dependency on automake which only has a  
> build dependency on autoconf. That means as soon as automake is  
> installed, a user would be perfectly free to uninstall autoconf and  
> expect no problems. And once libtool is installed, the user would  
> expect to be able to uninstall automake with no problems. And  
> MacPorts will allow uninstallation of those ports with no  
> complaints, since those ports are not library or runtime  
> dependencies but only build dependencies. So if you want to use  
> those ports to build something, you need to declare build  
> dependencies on them.

That's what I thought originally, but it didn't match with what I  
experienced (so can you explain this behavior):

~ $ sudo port -v uninstall xorg-xproto
--->  Unable to uninstall xorg-xproto 7.0.14_1, the following ports  
depend on it:
--->    Xft2
--->    xorg-libXau
Error: port uninstall failed: Please uninstall the ports that depend  
on xorg-xproto first.

(16:10:59 Fri Dec 05 2008 jeremy at tifa i386)
~ $ grep -C2 xorg-xproto src/macports/trunk/dports/x11/xorg-libXau/ 
Portfile

depends_build   port:pkgconfig \
                 port:xorg-xproto

> I'm not sure what you mean by triggering dependencies. I expect it  
> just runs "autoreconf". Is there more that's needed?

I meant does that also cause 'depends_build-append port:autoconf' to  
be run, or do I need to manage the dependencies still?

> There might be.
>
> Is "-fvi" something unique to this port or should this change be  
> made in MacPorts base?

I do it more for habit and consistency.  I just feel better knowing  
everything is being remade rather than testing if something is up to  
date beforehand.  It might be nice to do in base.