On Fri, Jan 23, 2009 at 02:53:59PM +0900, Charles Plessy wrote:
> I packaged a lot programs that have a test suite, and realised that, in order
> to run it after build, the dependancies of the binary package produced must be
> present as well. For the moment, I add them in Build-Depends(-Indep), but this
> is not satisfactory, because:
>
> - The build dependancy graph becomes unnecessarily complex when running the
> test suite is skipped.
I don't buy this argument, i.e., please expand it.
Build-Depends determines what is needed to completely perform the
process of turning a Debian source package into a set of Debian binary
packages. If that includes running tests, the test dependencies should
be mentioned there. If you are arguing that Build-Depends is too
coarse grained, and it might need a more precise splitting, according
to which debian/rules target build-dependencies are for, I might
concur. Still, the benefits of doing the needed split are not clear to
me.
> - Information is duplicated between Build-Depends: and the binary packages's
> Depends: field.
Uh? Why? In general test suite dependencies are not the same as binary
package dependencies, they might be:
- larger: due to the need of test framework which are not needed at
runtime
- smaller: due to part of the source code for which there are no tests
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
Attachment:
signature.asc
Description: Digital signature