Bug#41232: debian-policy: [PROPOSAL] Build-time dependencies on binary packages
> I´d prefer a syntax in the style of /etc/exports, e.g.
>
> Build-Depends: package1, package2(CPU1), package3(!CPU1),
> package4(SYSTEM2-CPU2, SYSTEM3-*), package5 | package6(CPU1),
> package7(CPU1, >= 2.0), package7(!CPU1, >= 2.1)
>
> It looks a bit easier to read (and create) to me than the prefix
> syntax as there is already a colon after "Build-Depends". If there
> is a system-cpu specification, it must be before the version
> specification, so a parser for this would not be too difficult.
Hmm... but the parser still has to decide if the thing in parens is an
arch spec or a version spec, which isn't really trivial, as the
version number can be an arbitrary string. I think I'm against this
just because it's too hard to parse.
> About the conflict headers: I don´t think they are necessary, so I
> vote for removing them from the proposal (as Richard suggested).
No, they're really necessary. An example is bash: If you have
termcap-compat installed during the build, configure will detect
libtermcap before libncurses and link everything with the obsolete
libtermcap. Therefore bash needs a Build-Conflict: termcap-compat.
Roman
Reply to: