[Buildd-tools-devel] Bug#500746: Bug#500746: feature request: use pre-existing schroot or run early script hook

Roger Leigh rleigh at whinlatter.ukfsn.org
Wed Oct 1 16:11:23 UTC 2008


On Tue, Sep 30, 2008 at 06:17:41PM -0700, Kees Cook wrote:
> Hello!  I'd like to have the ability to run commands within the chroot
> before building.  In a perfect world, I could specify a pre-existing
> chroot snapshot (one already started with schroot -b -c ....), and then
> I could open the chroot, run commands, run sbuild, and then destroy the
> chroot myself.  I imagine this looking like so:
> 
> $ CMDS=$(mktemp -t cmds-XXXXXX)
> $ echo "stuff to run...." > "$CMDS"
> $ CHROOT=$(schroot -b -c unstable-i386)
> $ schroot -u root -r -c "$CHROOT" "$CMDS"
> $ rm -f "$CMDS"
> $ sbuild -d unstable -c "$CHROOT" -A somepkg.dsc
> $ schroot -e -c "$CHROOT"
> 
> However, sbuild doesn't know how to look up this schroot nor to skip
> initialization, etc.

Could you possibly explain what exactly you would like to do with this
feature?  I would be happy to add some general mechanism to sbuild,
such as your patch, but I'd just like to understand the use case for it.

Are schroot setup scripts not an option, or do you need information
passing that only sbuild knows about?

Would you prefer to have sbuild call an external program, or would
enabling some sort of perl extension system using modules be acceptable?

Thanks for the patch.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.





More information about the Buildd-tools-devel mailing list