Hi J,
> Mine did not, but it got further:
ok
> couldn't find Rust. Then I actually read the Rust install output and
> put the darn path to rust and .cargo in my PATH!
I really don't understand where the rust requirement should come from
> Then I was missing the openssl-devel package in my 15.4 installation.
> mixer@mixerlinux:~ $ sudo zypper in openssl-devel
> After that:
> mixer@mixerlinux:~/kiwi $ tox -e devel
> devel create: /home/mixer/kiwi/.tox/3
> devel installdeps: -r.virtualenv.dev-requirements.txt
> devel develop-inst: /home/mixer/kiwi
> devel installed:
> alabaster==0.7.12,anymarkup==0.8.1,anymarkup-core==0.8.1,attrs==22.1.0,
> Babel==2.10.3,bleach==4.1.0,bump2version==1.0.1,bumpversion==0.6.0,cert
> ifi==2022.6.15,cffi==1.15.1,charset-
> .
> .
> .
> devel: commands succeeded
> congratulations :)
yep that is how it should look like. Usually the tox setup is
straight forward but there is one problem with tox. It does resolve
nicely within the python module requirements but if a python module
itself has dependencies to non-python libraries for example libopenssl
or some C library or any other component that is not python, tox
will not be able to resolved this (how should it) and then the install
of that python module failed. Even more of a problem is, if a python
module has some external object reference and can't find it, it tries
to compile it themselve. This means all the headers and dev-libs
becomes a requirement as well. To make this a bit easier for users
we provide a helper script that installs the non python requirements
distinguished by distro here:
https://github.com/OSInside/kiwi/blob/master/helper/install_devel_packages.sh
We also document that step in the contributing chapter here:
https://osinside.github.io/kiwi/contributing.html
In your case it seems we are missing some stuff ?
> Now onto actually making some doc changes (and maybe some code changes
> too...)
Sounds great, thanks in advance