Bug#604397: Request for TC to rule on a course of action for supporting build-arch

[Guillem Jover <guillem@debian.org>]

On Mon, 2011-06-06 at 15:59:15 +0200, Bill Allombert wrote:
> On Mon, Jun 06, 2011 at 12:09:34PM +0200, Bill Allombert wrote:
> > On Mon, Jun 06, 2011 at 02:15:37AM -0700, Steve Langasek wrote:
> > >  1) Implement support for calling 'debian/rules build-arch' in place of
> > >     'debian/rules build' by checking for the presence of the target using
> > >     'make -qn'.[1]
> > > 
> > >  2) Implement support for calling 'debian/rules build-arch' with a fallback
> > >     to 'debian/rules build' by checking whether the output of the build-arch
> > >     target matches that of a dummy target.[2]
> > > 
> > >  3) Implement support for calling 'debian/rules build-arch' in place of
> > >     'debian/rules build' if a Build-Options field is set in debian/control
> > >     of the source package specifying that this target is supported.[3]
> > 
> > For the record, I have been working to the patch that implement 3) to get accepted,
> > see bug #229357.
> 
> Still for the record this patch has been accepted in dpkg as of today:
>     http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=14d48ef
> Does that make this bug moot for all concerned ?

FWIW, I don't agree with that change. If we'd decide to go with
non-mandatory support, I'd rather use one of the autodetection
options, preferably the “make -qn” one which would allow us to warn
the user for the cases where it makes sense to add the targets.

regards,
guillem