Hi Matthias (2024.08.16_12:58:22_+0200) I tried to set you up with some questions that were easy to answer here, without trying to push any solution.
Answering them would help the committee to understand the options on the table, and probably help the Kernel team to understand the problems with the current package structure. Let me repeat the questions, and you can check my assumptions: > Will it be another binary package in cross-toolchain-base, built from > linux-source-*? I'm assuming so? > Will cross-toolchain-base now contain linux-libc-dev-*-cross and > linux-libc-dev, as separate Arch: all, Multi-Arch: foreign binary > packages? I'm assuming linux-libc-dev-*-cross stay the way they currently are in cross-toolchain-base. You'd then add linux-libc-dev, Arch: any (as it used to be) Or maybe strip them down to dependency packages that depend on the cross package for each arch? > I don't know much about the stability of these headers, but I see > regular changes. I assume moving linux-libc-dev from the linux source > to cross-toolchain-base will mean that you'll have to do more frequent > uploads of cross-toolchain-base to keep them up to date, where this was > less critical for cross-compiler toolchains. > > What are the consequences of not staying up to date? I'm guessing > incoming bug reports from other packages wanting to use new features. I already put an assumption in there :P Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
