Package: debspawn Version: 0.4.0-1 Severity: wishlist Hi,
I usually build my Linux kernels in a chroot using make deb-pkg from the upstream makefile. This method means that there is no proper source package, and building one just to make debspawn happy to be able to build in a proper container instead of a chroot seems a bit overdone. I would still like to automatize the package build. For that, I need to - copy sources, helper stuff etc into the container after initiating the instance - execute a command inside that container debspawn's current method of operation that doesn't plan to leave a container linger around after debspawn's termination does not support this. Users of sbuild/schroot are going to stumble over that. It would be easier it debspawn would offer a bit more possibilities to interfere with the build process that is happening inside the container. For example, a hook could be called after unpacking the container's file system tree, telling it the location of the file system tree, so that the hook script could copy things into the container, probably including a script that would be executed inside the container before and after executing the actual package build. The actual copying could also be done by debspawn itself by having a directory like /var/lib/debspawn/injected-files and having the contents copied by debspawn itself, but this would probably make it necessary to copy the (potentially big) files twice. I could of course build a big, temporary source package, but that would mean, in my case, to (needlessly) tar/zip up the kernel sources into my local source package just to have them unpacked inside the container again. With a hook, I could copy the unpacked kernel source tree or the original linux.tar.xz into the containe before the build is initiated. Please consider adding this as a feature. Unfortunately, I am not fluent enough in python to deliver a patch. Greetings Marc
