On Tue, 30 Oct 2018 at 17:23, Hugues Kamba <[email protected]> wrote:
> I am still new to Yocto but my understanding of adding pyvenv to venv's
> RPROVIDES is that python3-pyvenv is available (albeit as an alias of
> python3-venv).
> I therefore have not removed the possibility for one to choose to include the
> pyvenv package instead of the new venv package.
> In fact, I tested building with python3-pyvenv included.
> Which parts of the conmit message are contradicting according to you?
" This patch adds the python3-venv module as a self-contained package which
python3-pyvenv must depend on at run-time."
python3-pyvenv does't exist.
I'd simply rewrite the message along the follow lines:
python3: add python3-venv package
Package both the venv module and the pyvenv binaries into the
python3-venv package.
Add python3-pyvenv RPROVIDES to python3-venv for backward compatibility.
Ross
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
