Build-Depends versioning and binary Depends versioning
Hi,
for a package I am working on, I am setting versioned Build-Depends, to
avoid using newer libav versions which would break compilation, e.g.:
libavcodec-dev (<< 6:9)
Compilation under pbuilder for Sid goes fine, but the binary packages
are still allowed to be installed with newer libav binary packages:
libavcodec53 (>= 6:0.8.3-1~) | libavcodec-extra-53 (>= 6:0.8.5)
As you can see I can still install the package on a system which has
libavcodec53 9.3-1 from experimental, as the binary dependency is
just greater than, the strictly minor one from the Build-Depends didn't
propagate to the binary packages.
Thinking about it I can see why this is happening: I specified the
Build-Depends for the -dev packages, not for the corresponding
libraries, but naively I thought the build system can figure out the
relationship between the two.
Should I restrict the Depends for the binary packages by hand in
debian/control? For example adding:
libavcodec53 (<< 6:9)
to the binary package I am interested in restricting?
For reference this is the debian/control file of the package:
http://git.ao2.it/libam7xxx.git/blob/6d2d8613958e1f0ef011e9d848426086caafe9db:/debian/control
The doubt is about the libam7xxx-bin package.
Tell me if you need more details or if I was not clear enough.
Thanks,
Antonio
--
Antonio Ospite
http://ao2.it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Reply to: