Bug#738552: autopkgtest: add support for using locally-built binaries without a second build

Antonio Terceiro terceiro at debian.org
Tue Feb 11 13:59:27 UTC 2014

On Tue, Feb 11, 2014 at 07:03:08AM +0100, Martin Pitt wrote:
> Hey Antonio,
> Antonio Terceiro [2014-02-10 15:53 -0300]:
> > > Perhaps there is some middle ground, like adding a --binary-dir=<dir>
> > > which acts like "--binary <dir>/<x>.deb" for each <x>.deb in <dir>?
> > 
> > that would be nice, yes. I would just restrict the list to binaries that
> > could be the product of building the current tree (i.e. the binaries
> > listed in a .changes file in <dir> corresponding to the current version
> > of the source package pointed by --built-tree=.)
> I think the .changes actually the right place. So this could become a
> new option
>   --changes ../foo_*.changes
> which would be implied if you specify a *.changes file (much like
> .deb, .dsc, etc.), so you'd call this with
>   adt-run ../foo_*.changes
> to run tests from the .dsc and with the binaries in the .changes, or
>   adt-run ../foo_*.changes ./
> to run tests from the built tree in the current directory, and with
> the binaries in the .changes.
> That is easy to use, fits into the design of the existing processing
> options, and does not change existing behaviour. What do you think?

awesome! :-)

Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20140211/a42d933e/attachment.sig>

More information about the autopkgtest-devel mailing list