numba and llvmlite versioning

[LebedevV]

Package

dev-python/numba-9999

What happened

Can we add somehow a trigger to rebuild llvmlite-9999 when emerging dev-python/numba-9999 ?

Expected behaviour

No response

emerge --info

-

Build log (or relevant tail)

-

Upstream bug report

No response

Additional context

No response

[istitov]

Thanks for the report!

Portage can't do the literal thing here: rebuilds only propagate dependency -> dependent (a consumer is rebuilt when its provider changes), never the reverse.
So there's no ebuild hook that makes emerge numba-9999 rebuild llvmlite-9999.

For keeping the two live ebuilds current with upstream main together, the idiomatic tool is app-portage/smart-live-rebuild -> emerge @live-rebuild, which rebuilds every -9999 whose VCS head advanced - picking up numba and llvmlite in one pass.

Here I added is the ABI coupling in the direction Portage does support: llvmlite-9999 now carries an LLVM-major subslot
(SLOT=0/${LLVM_COMPAT[0]}) and numba-9999 depends on ~dev-python/llvmlite-9999:=. So when llvmlite is rebuilt against a different LLVM -- e.g. once #275 lands and flips it 20->22 -- numba is rebuilt against it automatically.

[istitov]

so check it out, please!