As mentioned in the last development meeting, I have been exploring the idea of replacing pbuild with sbuild in our CI system, because: * sbuild uses plain chroots that are stored uncompressed, so spinning up a sbuild instance is instant and makes very little IO. * sbuild uses cow on shm if there is enough memory, which speeds up things significantly, and remove the need to use hacks like eatmydata. * The setup and usage is simpler, I was able to build trisquel packages on it without any change from default configs and setup. * chroots are kept updated automatically
The way I have tested it is with the attached script, which creates the necessary chroots in /var/lib/schroot/chroots. Sbuild provides a command that does this in one go, but it would need some changes to support Trisquel, so I wrote that simple script in the meantime. After running it, these are the main commands: # list chroots schroot -l # start a shell on a chroot sbuild-shell flidas-amd64 # build a package sbuild -d flidas /path/package_1.0.dsc --arch=i386 The last command will build the package and copy the result files in the same path where the dsc and tarballs were. There are parameters to set gpg signing, number of parallel jobs, logging, and many others.
sbuild-create.sh
Description: application/shellscript
_______________________________________________ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
