Bug#217945: dpkg-dev: should depend on build-essential
clone 217945 -1
reopen -1
retitle -1 Remove mention in dpkg-buildpackage manpage about checking for build-essential
severity -1 important
thanks
On Tue, 4 Nov 2003, Julian Gilbey wrote:
> > We used to do this. But Wichert convinced me it was wrong, and the change was
> > backed out.
>
> (1) You should then back out the change to the dpkg-checkbuilddeps
> manpage as well.
Ah, yes. Wichert overlooked that when he backed it out.
>
> (2) If it is not for dpkg to enforce policy, why run
> dpkg-checkbuilddeps during dpkg-buildpackage, with an abort on
> error?
Because that's not policy, but a dpkg interface.
> (3) A happy compromise could be for dpkg-checkbuilddeps to check for
> the presence of build-essential (or for the build-essential
> dependencies) and to warn (only) if any are not found, rather than
> to exit with an error.
Again, that's debian policy.
Reply to: