Simon Richter <[EMAIL PROTECTED]> writes:
> Hi,
>
> Andreas Metzler wrote:
>
>> ---------------
>> Somehow make dpkg-buildpackage -B make use of the build-arch target
>> if present. Either by detecting it automatically or by something like
>> #229357.
>> ---------------
>
> The entire issue circles around not being able to reliably detect
> whether the target is present using a simple script. But who said it
> has to be a script?
>
> Proposed alternative solution:
>
> 1. hack GNU make to support a "--has-target" option that returns an
> appropriate return code (hey, it's free software, after
> all!). Proposed return codes are 0 (yes), 1 (no) and 2 (error).
>
> 2. make "dpkg-buildpackage -B" use this facility to determine whether
> the target is present. If yes, use the "build-arch" target to build;
> if no, use the "build" target after printing a warning.
>
> 3. grep the build logs for warnings about missing "build-arch" target,
> add an entry to the TODO list on the package overview page on
> qa.debian.org and to DDPO.
>
> The only remaining question is what should happen with build failures
> in packages that provide a non-functional "build-arch" target. In my
> opinion, this is a genuine bug, even if policy can be read in a way
> that makes it disagree.
>
> Simon
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
There are two points to this:
1.) don't call build so build-indep is not called
2.) have Build-Depends only contain packages needed for build-arch and
binary-arch
The seconds part requires that tools like sbuild and pbuilder know
beforehand if build or build-arch will be used. Running debian-rules
can always have side effects and can actively rely on them so a
"--has-target" can not be implemented cleanly in make.
So you missed the point.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
