<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Please prefer pkg-config over python-config" href="https://bugs.freedesktop.org/show_bug.cgi?id=57800#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Please prefer pkg-config over python-config" href="https://bugs.freedesktop.org/show_bug.cgi?id=57800">bug 57800</a> from <a class="email" href="mailto:mgorny@gentoo.org" title="Michał Górny <mgorny@gentoo.org>"> Michał Górny</a> <pre>(In reply to <a href="show_bug.cgi?id=57800#c1">comment #1</a>) > That would simplify a lot of things for us. But it seems to be only > available from 2.7, but we support 2.6 now. I guess we could drop support > for 2.6. Well, as the summary states, I was suggesting using it and default and having a fallback to python-config. But either way's fine, I think. > One advantage of python-config is that it is easy to go from python-config > to python by simple string substitution. Let's say that I detect flags and > libs for some python. How do I know which binary to call? I'd say it's just another substitution. Since you would call: $ pkg-config --libs python-${PYTHON_VERSION} You could just go for: python${PYTHON_VERSION} However, I'm not sure where you would need that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>