schroot default chroot path (was: Re: Intent to commit craziness - source package unpacking)
josch at debian.org
Wed Nov 30 11:18:54 UTC 2016
Quoting Ian Jackson (2016-11-30 12:11:22)
> ~Johannes Schauer writes ("Re: Intent to commit craziness - source package unpacking"):
> > sbuild supports multiple backends. The default backend is schroot. How to get
> > from "apt-get install sbuild" to actually building packages depends on the
> > backend used. For the default schroot backend, sbuild provides the
> > sbuild-createchroot tool which runs debootstrap and creates a schroot config
> > file. So if you stay with the defaults, then you run:
> > $ apt-get install sbuild
> > $ sbuild-createchroot unstable /srv/chroot/unstable-amd64
> WIBNI the final argument had a default ? :-)
it would. If anybody knows a good argument for a default location for schroot
containers then I can add such a default. I am not aware of such a standard
path for system-wide schroot directories or tarballs.
Anybody with a good argument for such a default location can feel free to open
a wishlist bug against sbuild and then we can discuss this there. Probably good
to do this together with the schroot maintainer (Roger Leigh in CC).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
More information about the vcs-pkg-discuss