|author||Sean Whitton <email@example.com>||2018-06-21 13:27:41 +0100|
|committer||Ian Jackson <firstname.lastname@example.org>||2018-06-21 14:14:39 +0100|
dgit-user(7): Suggest sbuild-debian-developer-setup(1)
This will only create the chroot for building packages for the machine's architecture, because sbuild-debian-developer-setup(1) does not have an --architecture option, so sbuild-createchroot(1) will be needed too, hence the 'and'. The nice thing about sbuild-debian-developer-setup(1) is that does fiddly things that a non-expert might forget about, like adding the current user to the sbuild group. So it is still worth recommending even though it does not have an --architecture option. Closes:#895779. Signed-off-by: Sean Whitton <email@example.com>
Diffstat (limited to 'dgit-user.7.pod')
1 files changed, 3 insertions, 2 deletions
diff --git a/dgit-user.7.pod b/dgit-user.7.pod
index c74396a..5713064 100644
@@ -367,8 +367,9 @@ have enabled.
You'll need a chroot for each of the secondary architectures.
This is somewhat tiresome,
even though Debian has excellent tools for managing chroots.
-C<sbuild-createchroot> from the sbuild package is a
-good starting point.
+C<sbuild-debian-developer-setup> from the package of the same name
+and C<sbuild-createchroot> from the C<sbuild> package are
+good starting points.
Otherwise you could deinstall the packages of interest
for those other architectures