Bug#218893: Autodetecting existence of build-arch target
On Wed, May 05, 2004 at 05:34:10PM +0200, Bill Allombert wrote:
> On Wed, May 05, 2004 at 11:46:20AM +0200, Andreas Metzler wrote:
> > I have recently asked Scott James Remnant[1] on IRC for comments on this
> > problem and the proposed solution (#229357), to add Build-Options:
> > build-arch' to debian/control if the package supported this target.
> > I gathered that he was not in favour of it and prompted for alternate
> > solutions he suggested
> > make -f debian/rules -pn | grep '^binary-arch:'
> I hope you meant
> make -f debian/rules -pn | grep '^build-arch:'
> since binary-arch is mandated by policy already.
Of course.
[...]
> The apparent benefit of this technique is that it will not require
> packages to be modified to take advantage of it.
>
> But in practice this is not true:
> Only packages that currently FTBFS would work unmodified. All others
> will need to be modified to resplit Build-Depends-Indep from
> Build-Depends before build-arch to be really useful.
> And that will not fix buildd either: the implied assumption that
> Build-Depends-Indep imply build-arch is not warranted by policy.
Policy is simply wrong in this respect, because it does not describe
the implemented behavior.
Just to recap: Afaik this bugreport is not about "Let us change the
buildds to follow policy." This bug is about making _one_ minimal
change:
Provide a way to make dpkg-buildpackage use "debian/rules build-arch"
if it exists instead of "debian/rules build".
[...]
> 2) buildd need to know whether it should install Build-Depends-Indep.
> Assuming Build-Depends-Indep split imply build-arch exist is not correct
> with current policy. This mean it must know whether dpkg-buildpackage
> will call build or build-arch. A control field is a clean way to do
> that.
[...]
I do not understand that. It is easy. If you use "dpkg-buildpackage
-B" binary-indep does not need to be installed, otherwise it does.
cu andreas
Reply to: