<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello Ryan,<div><br></div><div><br></div><div>Thanks for dealing with this! I did a quick search and I see 4 ports, including py-gobject3, with that issue. Shall I open a ticket about about it?</div><div><br></div><div><font face="Monaco">$ pwd<br>/opt/mports/trunk/dports/python<br>$ grep PKG_CONFIG_PATH */Portfile<br>py-gobject/Portfile: &nbsp; &nbsp;configure.env-append &nbsp; &nbsp;PKG_CONFIG_PATH='${python.prefix}/lib/pkgconfig'<br>py-gobject3/Portfile: &nbsp; &nbsp;configure.env-append &nbsp; &nbsp;PKG_CONFIG_PATH='${python.prefix}/lib/pkgconfig'<br>py-matplotlib/Portfile: &nbsp; &nbsp;build.env &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; PKG_CONFIG_PATH="${python.prefix}/lib/pkgconfig"<br>py26-mapnik/Portfile: &nbsp; &nbsp;configure.args-append &nbsp;PKG_CONFIG_PATH=${prefix}/lib/pkgconfig:${prefix}/Library/Frameworks/Python.framework/Versions/2.6/lib/pkgconfig/<br></font><br></div><div>Is the fix for all of these as simple as&nbsp;r120178 [1] like cal made?</div><div><br></div><div><br></div><div>Cheers!</div><div>Frank</div><div><br></div><div>[1] &lt;<a href="https://trac.macports.org/changeset/120178">https://trac.macports.org/changeset/120178</a>&gt;</div><div><br><div><div>On May 18, 2014, at 7:31 AM, MacPorts &lt;<a href="mailto:noreply@macports.org">noreply@macports.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">#43261: py27-gobject3: No package 'pycairo' found<br>---------------------------+----------------------<br> &nbsp;Reporter: &nbsp;ryandesign@… &nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Owner: &nbsp;cal@…<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Type: &nbsp;defect &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;Status: &nbsp;reopened<br> &nbsp;Priority: &nbsp;Normal &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;Milestone:<br> Component: &nbsp;ports &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;Version: &nbsp;2.2.1<br>Resolution: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;Keywords:<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Port: &nbsp;py-gobject3 &nbsp;&nbsp;|<br>---------------------------+----------------------<br>Changes (by ryandesign@…):<br><br> * status: &nbsp;closed =&gt; reopened<br> * keywords: &nbsp;lack-of-interest =&gt;<br> * resolution: &nbsp;worksforme =&gt;<br><br><br>Comment:<br><br> Ah, I had a local patch to the python-1.0 portgroup trying to solve the<br> problem I mentioned in comment:ticket:34271:12. I've been running with<br> that patch for a long time. I should just commit it.<br><br> The reason why py-gobject3 has a problem with the patch is that py-<br> gobject3 puts PKG_CONFIG_PATH into configure.env manually, instead of<br> using the configure.pkg_config_path variable. Looks like a number of ports<br> make this same mistake. However, after I commit my patch to the portgroup,<br> the ports will no longer need to add that path manually since the<br> portgroup will already have done it.<br><br>-- <br>Ticket URL: &lt;<a href="https://trac.macports.org/ticket/43261#comment:3">https://trac.macports.org/ticket/43261#comment:3</a>&gt;<br>MacPorts &lt;<a href="http://www.macports.org/">http://www.macports.org/</a>&gt;<br>Ports system for OS X<br>_______________________________________________<br>macports-tickets mailing list<br><a href="mailto:macports-tickets@lists.macosforge.org">macports-tickets@lists.macosforge.org</a><br>https://lists.macosforge.org/mailman/listinfo/macports-tickets<br></blockquote></div><br></div></body></html>