Use mmdebstrap as default
Necessary for grml-small. And generally a good idea.
@mika wrote:
I'm actually wondering whether we should drop cdebootstrap support, I never ever use that, I think it's worth dropping this?
Agree, we should probably drop cdebootstrap support. I think it's dead in Debian, too.
We should also considering dropping debootstrap support. Doing that will allow us being clear about the tool that will run, remove a config var, simplify the test matrix, etc. And IMO mmdebstrap is strictly the better tool - if available.
Doing that might mean killing support for running on stretch. Or we figure out what to do about --no-check-gpg for stretch's mmdebstrap.
Does debootstrap have better cross architecture build support?
Or qemu-debootstrap?
I think it's worth keeping support for changing debootstrap tool for future-proofness.
Switching the default however seems nice.
Does debootstrap have better cross architecture build support? Or qemu-debootstrap?
Even if they do, grml-debootstrap has IIRC no cross support.
grml-debootstrap has cross build support. Building ARM64 (on AMD64) was implemented here:
- https://github.com/grml/grml-debootstrap/issues/169
- https://github.com/grml/grml-debootstrap/pull/191
grml-debootstrap has cross build support. Building ARM64 (on AMD64) was implemented here:
Right. Then we should also run CI for that.