HI, Actually problem is not tools but documentation of recommended procedure. We need public encouragement to use current sbuild tool chain. (I didn't know it has evolved so much in last ? years.)
(Yes, I bare some responsibility...) On Sat, 2021-04-17 at 23:45 +0000, nerdymutualist wrote: > Hello Debian developers and maintainers, > > When I started to venture into building my own .deb packages, I > discovered that the process is (at least in my opinion) relatively > complex and arduous, and a variety of tools, sometimes overlapping, > exist to facilitate the process. On the other hand, Solus (another > distribution with which I have been involved in terms of packaging) > has a highly streamlined packaging process where most steps are > automated and the only input required is the URL of the source > tarball, the name of the package, and the steps to install the > program, and a tool called solbuild > (https://github.com/solus-project/solbuild) then uses OverlayFS to > make a container, download the tarball, run the installation steps, > detect which files were created by the installation script of the > software, and then build the package, all automatically without > requiring any sort of manual intervention. So I was thinking that > perhaps this approach might be applied to Debian to streamline the > packaging process and make it easier for people to contribute and > maintain packages. Do you think this would be a good idea? If so, I > would love to work on it (I am familiar with Go, Rust and Python). > > Thank you, > Jeremy (jwinnie) > Migrating from old pbuilder/cowbuilder practice to the current sbuild is what we need to promote. See: https://wiki.debian.org/sbuild (I updated this recently for source only upload compatible shape) sbuild default setting uses OverlayFS. Osamu
