Bug#191411: [proposal] build-depends-indep should not be satisfied during clean target
On Fri, Jun 06, 2003 at 06:31:31PM +0200, Bill Allombert wrote:
> > > I therefore propose the following change to section 7.6, which is a
> > > partial rollback from #164035:
> > >
> > > `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'.
> > > - `build', `build-indep', `clean', `binary' and `binary-indep'.
> > Seconded.
> Note that this policy change make a difference for
> arch: all source packages. For them, it is currently equivalent
> to use 'Build-Depends-Indep' and 'Build-Depends'
> With this change, it will no more be the case. Build-Depends will
> be safer since it cover clean (this trigger a lintian warning
> It can be worthwhile to state explicitly what happen for source
> arch:all packages in the policy.
He's right. Lots of Arch: all packages (correctly) use
Build-Depends-Indep and not Build-Depends at all. With this change to
policy, almost all of them will immediately cease being policy
compliant. (Most have debhelper as a dependency in the clean target.)
So what should this policy be? I understand the desire not to require
Build-Depends-Indep to clean, but this isn't quite the way to do it
Julian Gilbey, website: http://www.polya.uklinux.net/
Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/
Visit http://www.thehungersite.com/ to help feed the hungry