[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC] configure: prefer sphinx-build to sphinx-build-3
From: |
John Snow |
Subject: |
Re: [PATCH RFC] configure: prefer sphinx-build to sphinx-build-3 |
Date: |
Thu, 16 Apr 2020 14:22:32 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 |
On 4/16/20 8:31 AM, Alex Bennée wrote:
>
> John Snow <address@hidden> writes:
>
>> On 4/15/20 1:55 PM, Peter Maydell wrote:
>>> On Wed, 15 Apr 2020 at 18:33, John Snow <address@hidden> wrote:
>>>>
>>>> sphinx-build is the name of the script entry point from the sphinx
>>>> package itself. sphinx-build-3 is a pacakging convention by Linux
>>>> distributions. Prefer, where possible, the canonical package name.
>>>
>>> This was Markus's code originally; cc'ing him.
>>>
>>> (Incidentally I think when we say "Linux distributions" we
>>> really mean "Red Hat"; Debian/Ubuntu don't use the "sphinx-build-3" name.)
>>>
>>
>> I'll take your word for it :)
>>
>>> thanks
>>> -- PMM
>>> (rest of email untrimmed for context)
>>>
>>
>> My only goal here is that if you are using a virtual environment with
>> sphinx installed that it prefers that, so non-standard names need to
>> come last.
>>
>> There's probably 10,000,000 ways to do that, hence the RFC.
>
> What's wrong with just passing --sphinx-build=sphinx-build in your
> configure string? It will override whatever we auto-detect AFAICT.
>
My goal is to make virtual environments work out of the box.
I.e., if you run ./configure from inside a VENV, it should "just work."
--js