As I understand it, the following process is roughly what we're going
through for each binding to determine possible/actual install locations:
1. Query the (python/perl/ruby/php/...) interpreter to find the appropriate
directory that is in the interpreters search path by default, e.g.
On Thu, Dec 5, 2013 at 2:29 PM, Darryl L. Pierce dpie...@redhat.com wrote:
On Thu, Dec 05, 2013 at 01:57:22PM -0500, Rafael Schloming wrote:
snip
So overall I'd say this change should have some kind of switch to control
whether the QUERIED_LOCATION is used directly, and I'd argue that for
On Thu, Dec 5, 2013 at 1:57 PM, Rafael Schloming r...@alum.mit.edu wrote:
The primary benefit is that the build will adapt itself to the user's
environment. If the user has some custom python/ruby interpreter in their
path, it will configure and built itself against it and get the user up and
On Thu, Dec 05, 2013 at 02:41:53PM -0500, Rafael Schloming wrote:
On Thu, Dec 5, 2013 at 2:29 PM, Darryl L. Pierce dpie...@redhat.com wrote:
On Thu, Dec 05, 2013 at 01:57:22PM -0500, Rafael Schloming wrote:
snip
So overall I'd say this change should have some kind of switch to control
