X-RT-Original-Encoding: utf-8
Message-ID: <rt-4.4.1-42348-1504308268-1407.45407-0-0@isc.org>
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
X-Mailer: MIME-tools 5.508 (Entity 5.508)
MIME-Version: 1.0
References: <RT-Ticket-45407@isc.org>
 <rt-4.2.8-99962-1497890009-1430.45407-7-0@isc.org>
 <rt-4.2.8-23561-1497919501-1349.45407-7-0@isc.org>
 <rt-4.2.8-23561-1497939147-50.45407-7-0@isc.org>
 <20170621005615.3BCE07BFAA42@rock.dv.isc.org>
 <rt-4.4.1-1955-1498006580-286.45407-0-0@isc.org>
 <rt-4.4.1-1652-1503486623-1336.45407-0-0@isc.org>
 <rt-4.4.1-29645-1503663087-70.45407-0-0@isc.org>
In-Reply-To: <rt-4.4.1-29645-1503663087-70.45407-0-0@isc.org>
X-RT-Interface: Web
Content-Transfer-Encoding: binary
RT-Send-CC:
Content-Length: 739

Looks good to merge. manual testing succeeded.


On Fri Aug 25 05:11:27 2017, michal wrote:
> (The branch adds a new configure option, --with-python-install-dir.  It
> takes an absolute path as its argument as that is what the --install-lib
> option for setup.py uses.  The code in rt45407 is the simplest way I
> could think of to properly handle all of the following cases:
> 
>   1. --prefix not specified, --with-python-install-dir not specified
>   2. --prefix specified, --with-python-install-dir not specified
>   3. --prefix not specified, --with-python-install-dir specified
>   4. --prefix specified, --with-python-install-dir specified
> 
> where "proper handling" means "assuring the installed Python utilities
> are usable".)