Closed manut closed 2 years ago
I am not inclined to take this series because a deb package is really more than what is produced here. I do not see how this would benefit Elbe.
I hoped to describe the use-case properly in the commit message. I want to build a initramfs with elbe. The output shall be a deb package, that i can use it as a build-dependency in a kernel package. Is there another way in elbe to build a system with a custom elbe-based-initrd?
I get that. But that is not a complete Debian package as specified by the Debian Policy. No source package, probably no copyright file ...
Got it. Thanks for the clarification. If the argument is, that any debian package produced by elbe shall be following the Debian policy, we shall also overthink: https://github.com/Linutronix/elbe/blob/392d9ad148120283995bdba38b778059cb591e4f/elbepack/commands/toolchainextract.py#L60
What is the recommended way in elbe to use a custom initrd, eg. to use a overlayfs for /etc ?
You create a debian package that makes use of the update-initramfs hooks and install it in the system.
This will be a bigger rework of the bootup, since currently the initrd is compiled in the kernel. I tried to avoid this in the first step. It will also increase the RFS size a bit, but probably this could be fixed in finetuning.
For example initrd images might be used as input as build-dependency of a kernel package. Therefore implement a packer that is able to build simple debian packages.
Signed-off-by: Manuel Traut manuel.traut@mt.com