Re: PYTHON_FOR_BUILD_ONLY in lang/python/tool.mk

[Greg Troxel <gdt%lexort.com@localhost>]

Jonathan Perkin <jperkin%mnx.io@localhost> writes:

> * On 2023-11-22 at 11:55 GMT, Thomas Klausner wrote:
>
>>Should we replace this with USE_PYTHON with the allowed values of "build tool test run"?
>
> Yeh, ideally we'd have a much more orthogonal and understandable way
> of declaring exactly what we want from python.
n>
> Even after my change it's still confusing when packages include both
> tool.mk and application.mk because ordering matters, and if you
> include
> application.mk first then you end up with a full dependency, but last
> and you don't.

This is messy because at least my take on ordering is to have
tool_depends type stuff up top.

> And I'd like PYTHON_FOR_BUILD_ONLY=yes or USE_PYTHON=build to mean "do
> not buildlink".

I don't like PYTHON_FOR_BUILD_ONLY=yes as an expression as it seems
confusing.

I wonder if this is really specific to python, or if there's a larger
picture with "things that a package can depend on for various reasons".