Hello, > But dpkg-dev is built-essential, and so already installed > in the chroot, and so the edos-builddebcheck part should always > consider built-essential as installable, atleast for the usage > in wanna-build.
What should happen when a package has a *versionend* build-dependency on a package that is build-essential? Depending on the answer I see two different ways to implement this is in the edos-builddebcheck wrapper. If only a non-versionend build-dependency on a build-essential package should be considered always satisfied: in this case the wrapper should also generate a new package that provides all the build-essential packages. If any build-dependency on a build-essential package should be considered satisfied, no matter whether versionend or not: in this case the wrapper should just drop all the dependencies of build-essential packages. (This leaves the question open what to do with conflicts of build-essential packages, which is somewhat delicate when one really wants to treat correctly all the possible corner cases. This is probably not very relevant in practice). Kurt, which of the two possible behaviours would you expect? -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
