[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
Resolution:                |   Keywords:
      Port:  py-yaml       |
---------------------------+---------------------

Comment (by ryandesign@…):

 Replying to [comment:1 deric@…]:
 > I've investigated this by installing py27-yaml with libyaml not
 installed, and then installing libyaml specifically before I installed
 py27-yaml to see if there was some kind of opportunistic linking going on.
 But I can only get it to link against libyaml if I add the +libyaml
 variant.

 I've attached my log; perhaps you can compare it with yours.

 > As for if the variant should even exist, I'm not sure. It's an optional
 dependency and as such I usually like to have them turned off unless
 requested.

 Assuming the library provides the python module with ''some'' benefit,
 then it should probably be always on, otherwise ports that depend on the
 python module can't really rely on the library's presence.

 > In any case, when the libyaml dependency is included it should have the
 right supported_archs flag, would updating the Portfile with "i386 ppc
 ppc64 x86_64" for supported_archs when linking against libyaml be ok? I'm
 currently limited to a rMBP to actually test it on.

 That, or just put `supported_archs noarch` when the variant is ''not''
 selected.

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