Bug#41232: debian-policy: [PROPOSAL] Build-time dependencies on binary packages
Roman Hodek wrote:
> 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.
Yes, but a version specification starts with "<", "=" or ">" so it can
be decided at the first character and as I've suggested before the version
specification must be last inside the parenthesis.
> 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.
I think this should be handled in the build process itself (either
a configure option or patch configure itself) as I've already said when
I discovered the incorrectly built m68k binary, but the lpr/lprng example
convinced my that Build-Conflicts: is needed so I'm changing my opinion
here.
--
Stefan Gybas
Reply to: