[MacPorts] #25349: wine-devel should have a library dependency on port:xrender

[MacPorts]

#25349: wine-devel should have a library dependency on port:xrender
------------------------------------+---------------------------------------
 Reporter:  kthenriksson@…          |       Owner:  ryandesign@…           
     Type:  defect                  |      Status:  new                    
 Priority:  Normal                  |   Milestone:                         
Component:  ports                   |     Version:  1.9.1                  
 Keywords:                          |        Port:  wine-devel             
------------------------------------+---------------------------------------

Comment(by ryandesign@…):

 Replying to [ticket:25349 kthenriksson@…]:
 > The configure script explicitly checks for xrender, and so there should
 be a direct dependency.

 Perhaps. But as Joshua said, wine-devel depends on xorg-libXcursor which
 depends on xrender so there should not have been a problem.

 > In addition the direct dependency is needed for the new architecture
 checking magic to work properly.

 I don't think that's correct.

 Replying to [comment:2 kthenriksson@…]:
 > I noticed that my xrender -universal was not upgraded when I installed
 wine-devel, but it's possible that I had xorg-libXcursor +universal
 activated at the time, which would be why wine-devel did not touch
 xrender. So I guess the error was on my end.

 It should not have been possible for you to install xorg-libXcursor
 +universal if its dependency xrender was not installed universal. Did you
 install them with MacPorts 1.8.x or 1.9.x? 1.9.x should have definitely
 prevented the problem; if it was with 1.8.x I would have expected xorg-
 libXcursor to have failed to build.

 > It's long seemed strange to me though that dependencies don't care about
 ports being deactivated, only uninstalled. It seems like there should be a
 warning or an error to prevent the situation I got into with xrender
 above. If deactivating a port will break something, the user should be
 told I think.

 As of MacPorts 1.9, MacPorts does now warn if you try to deactivate a port
 that's being used by another port.

-- 
Ticket URL: <http://trac.macports.org/ticket/25349#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS