[MacPorts] #39205: py27-yaml links with libyaml even if the libyaml variant is not selected

[MacPorts]

#39205: py27-yaml links with libyaml even if the libyaml variant is not selected
--------------------------+---------------------
 Reporter:  ryandesign@…  |      Owner:  deric@…
     Type:  defect        |     Status:  new
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:  2.1.3
 Keywords:                |       Port:  py-yaml
--------------------------+---------------------
 py27-yaml links with libyaml even if the libyaml variant is not selected:

 {{{
 $ port -v installed py27-yaml
 The following ports are currently installed:
   py27-yaml @3.10_1 (active) platform='darwin 12' archs='noarch'
 $ port contents py27-yaml | grep so$
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/_yaml.so
 $ otool -L
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/_yaml.so
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/_yaml.so:
         /opt/local/lib/libyaml-0.2.dylib (compatibility version 3.0.0,
 current version 3.2.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 169.3.0)
 }}}

 Is there a reason why a user wouldn't want to use libyaml? Why not just
 always use it, and remove the variant?

 Also, you'll see the port claims to be noarch, but is clearly not:

 {{{
 $ lipo -info
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/_yaml.so
 Architectures in the fat file:
 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/_yaml.so are: x86_64 i386
 }}}

-- 
Ticket URL: <https://trac.macports.org/ticket/39205>
MacPorts <http://www.macports.org/>
Ports system for OS X