On Oct 11, 2009, at 11:10, Jack Howarth wrote:

On Sun, Oct 11, 2009 at 07:48:37PM +0200, Rainer Müller wrote:

Actually software should be asking python where it's headers are (by
using python*-config or requesting the path to
lib/python2.6/config/Makefile). The assumption of include/python* does
just not always hold true.

I could patch the Makefiles to execute python*-config within
the Makefiles but since MacPorts doesn't support packages as -py
variants like fink that seems rather pointless. I'll just change
the patch to redirect towards the headers and shared libraries
when I update the proposed packaging to build against python26.

Why not just fix it "the right way" and query python-config? That way if something changes in the future, it will "just work" and you can push that patch upstream, so others will inherit it as well...

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to