Bug#629385: Request for TC to rule on a course of action for supporting build-arch
On Sat, 11 Jun 2011, Steve Langasek wrote:
> This actually reads to me the same as option 1. What distinction are you
> meaning to draw here? It's not very "direct" use of build-arch if we're
> checking 'make -qn' first. The only other differences I see here are
> issuing a warning, and explicitly declaring to put this in policy now and
> that the auto-detection will eventually be deprecated. To me these all seem
> like implementation details that don't need to be ruled on in order for the
> TC to make its decision, but I'm also happy to have these spelled out in
> option 1 if that's the consensus.
As a dpkg co-maintainer, the implementation details matter to me. :-)
More seriously, the distinction I see is that with your option 1, it seems
like auto-detection ought be _always_ used in the future and that it's
perfectly fine to have only some packages implement
build-arch/build-indep.
I believe that auto-detection is a hack and to me it's only acceptable as
a temporary measure (i.e. until all packages support build-arch/build-indep).
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
Reply to: