On Sat, Feb 27, 2010 at 10:35:45AM +0100, Raphael Hertzog wrote: > forcemerge 480638 571671 > thanks > > On Sat, 27 Feb 2010, Kurt Roeckx wrote: > > It seems that for some reason dpkg-checkbuilddeps now adds the > > package "build-essential" to the Build-Depends, getting me: > > $ dpkg-checkbuilddeps > > dpkg-checkbuilddeps: Unmet build dependencies: build-essential > > This is a feature and not a bug, it's also hardly new. It has been there > for quite some time now. Merging with the pre-existing wontfix bug. > > > The package build-essential is not Build Essential, nor is it > > in my control file, nor do you Depend on it. > > We recommend it. Not all dpkg-* tools require this to be installed.
The argument seems to be that you require all build essential packages to be installed. They all are installed, it's just that build-essential is not installed. I also don't agree that build-essential should have the "Build-Essential: yes" tag. And it could go away if you add a Depends on build-essential. Following policy, build-essential should not be required because it's just a recommends. 99% of the users of dpkg-dev use it to build packages, so I don't see why this should be a recommends. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
