Hi Roger,
Roger Leigh wrote:
> I don't see why we can't just mandate it in Policy, and then
> enable it unconditionally if the Standards-Version is >= that
> policy version.
It seems that a summary of the previous discussion is in order.
dpkg 1.10.11~9 (In dpkg-buildpackage, call debian/rules -qn
build-arch, 2003-09-15) includes logic to check for the build-arch
target and use it if present. Unfortunately that logic was wrong.
Adam reasonably concluded (6acb249):
It is *not* possible *at all* to detect available targets
in a rules file. Period.
However, a couple of months ago, some code to do exactly that[1]
was written. So we can have a transitionless utopia, provided
this works. :)
Meanwhile there has been a lot of discussion of workarounds.
One is to use Standards-Version to indicate use of build-arch.
This seems to me like a terrible precedent to set: once you have
two features enabled this way, the transitions to use them
become coupled. Russ discussed[2] that in more detail recently;
many others have discussed it before[3].
Another is to introduce Build-options[3] to advertise support for
optional features like this (also DEB_BUILD_OPTIONS=parallel). Of
course, there is some relucance to do that when it is not clear it
is necessary.
Hope that helps.
Jonathan
[1] http://bugs.debian.org/598534
[2] http://lists.debian.org/debian-devel/2010/09/msg00648.html
[3] http://bugs.debian.org/218893
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
