On 26/02/25 12:29, Bastian Blank wrote:
I completely miss the reason why this can't be part of linux-headers and
just be used the same way.
Yeah, I should have explained my reasoning in my previous email.
The metapackage is added so users can choose whether to install the Rust
bits or not. If you think the user should not have this choice (I don't
disagree) then the metapackage is not needed. I'm not opposed to not
having the metapackage.
As for the actual contents of the package, the Rust bits, they are
binary files (and include an actual shared library), so my reasoning was
that they should belong to a different package than
linux-headers-@abiname@@localversion@, and be installed under /usr/lib
instead of /usr/src. This is what's currently being done for the kbuild
files.
So one alternative could be forgetting about the metapackage, only add a
new linux-librust-@abiname@@localversion@, and make
linux-headers-@abiname@@localversion@ depend on
linux-librust-@abiname@@localversion@ so that's pulled in automatically
with the headers (like kbuild is). Unless you are fine with
linux-headers-@abiname@@localversion@ also installing binary files, in
which case one can just add the Rust bits there. But I still think the
Rust bits should be installed in /usr/lib [1] instead of /usr/src.
[1] In the draft I'm using
/usr/lib/linux-librust-@abiname@@localversion@ as installation path.
