On Sat, 26 Oct 2013 14:14:23 +0200 Guillem Jover <guillem@debian.org> wrote:
> Hi!
>
> On Thu, 2013-10-24 at 15:47:56 +0100, Ximin Luo wrote:
> > Package: debian-policy
> > Severity: normal
>
> > I was recently told to split part of my Build-Depends field into a
> > separate Build-Depends-Indep field. Not one to follow orders without
> > question, I went and did some research, and found this snippet in
> > the policy[1]:
> >
> > "There is no Build-Depends-Arch; this role is essentially met with
> > Build-Depends. Anyone building the build-indep and binary-indep
> > targets is assumed to be building the whole package, and therefore
> > installation of all build dependencies is required.
>
> dpkg has supported Build-Depends-Arch and Build-Conflicts-Arch since
> 1.16.4 (complete support with 1.17.0). Although they should not be
> used yet, as long as other resolvers are not aware of these.
>
> Thanks,
> Guillem
>
>
Hi Policy maintainers,
With dpkg and buildds supporting build-arch and build-indep plus source
uploads being tested in unstable, perhaps it is time to move forward
with this again? :)
The build options are currently:
1. Maintainer uses binary and build targets (i.e. *-arch AND *-indep)
- buildds uses binary-arch and build-arch missing architectures
2. Maintainer uses binary-indep and build-indep targets
- buildds uses binary-arch and build-arch on *every* architecture
(Ben Hutching has been doing this for a while already)
3. Maintainer uploads a source only (*)
- One buildd uses binary-indep and build-indep to build the arch:all
packages (if present)
- buildds uses binary-arch and build-arch on *every* architecture
(*): Being tested in experimental atm.,
As noted, only option 1 uses the binary and build target.
Thanks,
~Niels
Please CC me on replies.
Attachment:
signature.asc
Description: OpenPGP digital signature