Simon McVittie <smcv <at> debian.org> writes: > (I would recommend that porters doing manual builds use sbuild if at all > possible, though, to be as close as possible to what a buildd would have > done.)
On the other hand, porters are often packagers, and many packagers are much more familiar with cowbuilder or pbuilder as it’s *much* simpler to set up, and also provides good isolation. The chroots themselves are mostly identical – especially if the pbuilder-satisfydepends-apt patch will be applied by the maintainer, please, to get rid of aptitude. (There’s pbuilder-satisfydepends-classic which also does not use aptitude, but is slower. But useful for when aptitude is not installable for some time.) Porter uploads are usually done when the archive is in a state such that buildds cannot work. In these states, getting sbuild and schroot to work is virtually impossible; see their build- and runtime dependencies for why. Especially Boost is… not a nice thing. Just food for thought. bye, //mirabilos -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/loom.20140325t142205-...@post.gmane.org
