[buildd-tools-devel] Bug#859867: Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

[Johannes Schauer]

Hi,

Quoting Michael Stapelberg (2017-04-08 11:28:12)
> One area where sbuild sorely lacks is configuration, though: pbuilder is very
> easy to set up, whereas sbuild requires reading through
> https://wiki.debian.org/sbuild, performing a bunch of steps, only to end up
> with a setup which works fine for unstable, but seems very clumsy when
> building packages for experimental or backports.
> 
> One solution to this issue that I can see is to add a new binary
> package to src:sbuild which — possibly after a brief debconf prompt —
> performs all the necessary steps to end up with a setup that just
> works.
> 
> What are your thoughts on this? Would patches be welcome to add such a
> package?

patches totally welcome! :D

This is a nice idea!

Maybe these packages could be named sbuild-backend-${foo} where $foo is the
respective backend? At first, a package sbuild-backend-schroot would be cool
because schroot is the default backend. It would be nice if that would set up
sbuild schroots for stable-backports, unstable and experimental. Maybe that
package should also install and activate cron-jobs to regularly update those
schroots?

What irks me is, that this setup would be Debian specific. It doesn't make much
sense for Debian's downstreams to have have schroots for Debian. Maybe the
distribution name should be part of the package name? Or maybe it should be
easy for downstreams that care to override the set of distributions the
schroots are created for?

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20170411/985cf231/attachment.sig>