On Mon, Feb 10, 2014 at 05:08:42PM +0100, Martin Pitt wrote: > Hey Antonio,
Hello Martin,
> Antonio Terceiro [2014-02-10 12:52 -0300]:
> > I can use --binary, but that's error-prone and a little difficult when
> > you have multiple binary packages in a source.
>
> You don't need to explicitly specify "--binary", merely adding
> something like
>
> adt-run ../*.deb --built-tree=. [...]
>
> will do.
ah! that's nice, and solves my use case for now.
> > IMO it would make a lot of sense for --built-tree to use the
> > locally-built packages to satisfy test dependencies.
>
> That would introduce the assumption that the binaries are present in
> ../ (which isn't the case if you just do debian/rules build, or use
> {git,svn,bzr}-buildpackage and have them in /tmp/build-area/ or so)
> and actually match the currently built tree.
>
> It would also change the current behaviour, which should at least get
> an opinion from Ian.
sure - we probably don't want to change existing behaviour.
> 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=.)
a very naive approach I am using for now is (in shell):
version=$(dpkg-parsechangelog -SVersion)
binaries=$(for pkg in $(dh_listpackages); do echo
"../${pkg}_${version}_*.deb"; done)
adt-run $binaries --built-tree . --- adt-virt-schroot unstable
> But then again, this is even more complicated than just specifying
> "<dir>/*.deb".
it is, but when you have several source packages in the same parent
directory ../*.deb will bring binaries from all of them
--
Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
