On 26/02/25 19:47, Miguel Ojeda wrote:
On Wed, Feb 26, 2025 at 7:24 PM NoisyCoil wrote:
It does indeed depend on the configuration, because at least some
abstractions are enabled via the configuration and different metadata
will be produced depending on whether they are or not (Miguel should
On 26/02/25 13:40, Miguel Ojeda wrote:
Ah, and by the way, there will likely be way more `.rmeta`s and `.so`s
generated (and where they get placed will change) in the future, since
the system will change, so please keep that in mind (e.g. perhaps try
to avoid hardcoding details and/or overfitting
On 26/02/25 14:22, Bastian Blank wrote:
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.
There is no need to get picky, sorry.
No need to be sorry, this is the kind of feedback I am looking for. If
you confirm
Hi Ben,
On 26/02/25 19:11, Ben Hutchings wrote:
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.
It does indeed depend
On 26/02/25 19:10, Miguel Ojeda wrote:
On Wed, Feb 26, 2025 at 3:15 PM NoisyCoil wrote:
Yeah I'd imagined this could happen. Currently d/rules just copies
rust/{*.rmeta,*.so} into the destination directory. My guess was that in
the future they could be placed in subdirectories of rust/, b
Hi kernel team!
I know this is early to say the least, but I would like to ask your
opinion on the naming of a package that could eventually end up in the
official Debian kernel packaging.
As is the case for C, building out-of-tree kernel modules written in
Rust [1] requires some extra file
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
On 06/03/25 14:25, Lorenzo wrote:
Hello Otto,
[please keep me in CC, I'm not subscribed]
Salsa CI has had for many years the job 'missing-breaks' that
complements piuparts by checking that the files a package introduce
don't clash with files shipped by any other package in the
distribution wit
On 06/03/25 17:09, Bastian Blank wrote:
Open an serious bug report against oss4-dev. No need to wait, it needs
to go.
oss4-dev is fine (unless diversions of files in linux-libc-dev are
forbidden): oss4-dev is correctly diverting the header, as a consequence
it needs not Break or Conflict wit
9 matches
Mail list logo
