Bug#186809: dpkg-dev: dpkg-buildpackage should minimize build dependencies
On Sat, Mar 29, 2003 at 11:54:35PM -0500, Jean-Michel Kelbert wrote:
> Le 29/03/03 à 23:48 Adam Conrad (adconrad@0c3.net) écrivait :
> > /don't/ end up doing that. I don't need dpkg-buildpackage warning me about
> > this. What does it hurt to have them listed twice? The package will only
> > download and install once on autobuilders, afterall. :)
>
> You are true, there are some package where it is a necessity to have
> such dependency. But I only say "warn". It will only warn the user, and
> maybe it will think about it. And to my mind in most case this would be
> helpful.
Non-minimal build-dependencies are a frequent case, called out
specifically in policy. Warning about them would be misleading, and
would lead to maintainers wrongly "optimizing" their build-dependencies
when they should instead be stating exactly what their package requires.
This in turn would lead to more packages failing to build when some of
their build-dependencies have their dependencies rearranged, which leads
to more serious bugs, which leads to more work for everyone.
In short: this is a bad idea, please don't do it ...
Cheers,
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: