Technically I believe that to build a source package, you need to install build dependencies and run the clean target first (which may depend on build dependencies). This may for example produce a control from a control.in, or similar, via a build dependency. That's why we're doing this in a container by default.
In the common case you can get away without this, but I wanted to avoid having to give first time contributors excuses about why the default case doesn't work. So I'm going for a container-based build being the default so that all source packages in the archive (including historical ones where possible) can be built without exception as much as possible.
I expect experienced developers will want to use --no-lxd by default. I intend for there to be some kind of per-user configuration option to make this this automatic for them.
This is currently by design, so this is Invalid I think. But I appreciate your option. Feel free to tell me why I'm wrong right here :)
Technically I believe that to build a source package, you need to install build dependencies and run the clean target first (which may depend on build dependencies). This may for example produce a control from a control.in, or similar, via a build dependency. That's why we're doing this in a container by default.
In the common case you can get away without this, but I wanted to avoid having to give first time contributors excuses about why the default case doesn't work. So I'm going for a container-based build being the default so that all source packages in the archive (including historical ones where possible) can be built without exception as much as possible.
I expect experienced developers will want to use --no-lxd by default. I intend for there to be some kind of per-user configuration option to make this this automatic for them.
This is currently by design, so this is Invalid I think. But I appreciate your option. Feel free to tell me why I'm wrong right here :)