"Kurt B. Kaiser" <[EMAIL PROTECTED]> wrote: > The QA upload switched from Build-Depends-Indep to Build-Depends and > I left that alone. Maybe both of these (identical) should exist? > Build-Depends: debhelper is necessary because dh_clean is in the clean > target, and Build-Depends-Indep might be needed since binary-indep > calls dh_* commands. It's not clear to me; enlightenment would be > appreciated!
Here are a few messages on the matter that I found helpful, and thus kept for reference. HTH. http://lists.debian.org/debian-policy/2003/debian-policy-200309/msg00067.html ,---- | Something like... | | `` 'Build-Depends' should contain all packages that are required for a | 'dpkg-buildpackage -B' run to complete successfully. Any packages | that are not requird for a 'dpkg-buildpackage -B' run, but that are | required for a plain 'dpkg-buildpackage' run should be put in | 'Build-Depends-Indep'. For reference, 'dpkg-buildpackage -B' calls the | 'foo', 'bar', and 'baz' targets of the 'debian/rules' file, whereas | 'dpkg-buildpackage' calls the 'foobar', 'quux', and 'quuux' targets.'' | | (dpkg-buildpackage's manpage doesn't tell which targets exactly are | called. If people accept the above, I'll make sure I find out, but I was | too lazy to read the code right now) | | -- | Wouter Verhelst | Debian GNU/Linux -- http://www.debian.org | Nederlandstalige Linux-documentatie -- http://nl.linux.org | "Stop breathing down my neck." "My breathing is merely a simulation." | "So is my neck, stop it anyway!" | -- Voyager's EMH versus the Prometheus' EMH, stardate 51462. `---- http://lists.debian.org/debian-devel/2003/debian-devel-200310/msg01460.html ,---- | Scott James Remnant <[EMAIL PROTECTED]> wrote: | > On Sun, 2003-10-19 at 09:51, Adam Conrad wrote: | [...] | >> libtool fails to build from source on all the buildds[1] due to a missing | >> build-dep on texi2html. | | [...] | | > My reading of policy suggests that this is correct: | | > ----8<--------8<--------8<--------8<--------8<--------8<--------8<-------- | > `Build-Depends-Indep', `Build-Conflicts-Indep' | > The `Build-Depends-Indep' and `Build-Conflicts-Indep' fields must | > be satisfied when any of the following targets is invoked: | > `build', `build-indep', `binary' and `binary-indep'. | > | | [Flo] The following footnote is *not* part of the Debian Policy (see | above for the footnote mark). | | > [1] If you make "build-arch" or "binary-arch", you need Build-Depends. If | > you make "build-indep" or "binary-indep", you need Build-Depends and | > Build-Depends-Indep. If you make "build" or "binary", you need both. | > ---->8-------->8-------->8-------->8-------->8-------->8-------->8-------- | | > texinfo and texi2html are used in the "build" target. As far as I can | > tell this means that the buildd should be ensuring both Build-Depends | > and Build-Depends-Indep are installed before running it. | | > Have I read policy wrong, or is policy not entirely in accord with | > reality? | | [...] | | Afaik the latter, the buildds don't build the binary-all target and | won't install Build-Depends-Indep. | | This works: | * If your package only builds arch-dependent packages, don't use | Build-Depends-Indep | | * If your package only builds binary-all packages, you can choose | whether to use Build-Depends-Indep or Build-Depends. However many | packages need Build-Dependencies for the clean target (dh_clean), if | this applies you must use "Build-Depends". | | * If your package builds both binary-arch and binary-all packages, | list anything needed for build, clean, build-arch and binary-arch in | "Build-Depends" and anything _additionally_ needed for binary-indep | in "Build-Depends-Indep". `---- -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
