Open wolfv opened 2 months ago
If conda-build encounters a situation where no host is present, it handles build as host.
I think this was the original behavior in conda-build 2.x
where host
didn't exist yet.
There are a few recipes (2k+!) that do not use host
in conda-forge.
I think treating build as host is very unintuitive. I wouldnt copy that behavior. The conversion tool should be able to correct this.
We currently don't handle
build
&host
the exact same way asconda-build
does.If conda-build encounters a situation where no
host
is present, it handlesbuild
ashost
. This probably happens most often fornoarch
packages where nothing is linked against and cross-compilation is no concern.I am wondering if we should follow that behavior, or if we should just make sure that
pip install
installs into the$PREFIX
(we could export thePIP_PREFIX
variable for that ... possibly!).In that case, pip would always install into the correct prefix.