On Wed, 2025-02-26 at 13:40 +0100, Miguel Ojeda wrote: > On Wed, Feb 26, 2025 at 1:13 PM NoisyCoil <noisyc...@disroot.org> wrote: > > > > 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. > > Yeah, there are different viewpoints. > > The `.rmeta` are binary, in that they cannot be easily read at all, > but on the other hand they are not fully build object files either. > They are acting here like C headers, i.e. containing the same sort of > information from other TUs/dependencies, so in that sense it makes > sense for them to be there. > > The `.so` is definitely a built binary, but it is also "like a header" > in the sense that it contains macros that in the C world would have > been in a header. [...]
This shouldn't go in a linux-headers package, because we aim to support cross-builds of modules. If it doesn't depend on the kernel configuration (aside from CONFIG_RUST being enabled) then it belongs in linux-kbuild. Ben. -- Ben Hutchings All the simple programs have been written, and all the good names taken
signature.asc
Description: This is a digitally signed message part
