On Sat, May 15, 2010 at 08:03:25PM +1000, Mark Purcell wrote:
On Saturday 15 May 2010 07:22:55 Eugen Dedu wrote:I still do not understand, could you please elaborate? On the system where libopal is linked to srtp, libopal-dev too uses srtp.Opal .debs get built on a machine (user, binNMU, buildd) with srtp-dev installed.These .debs then get installed on a machine without srtp-dev. You would be surprised how often this can occur. No deps automatically pull in srtp libs.User then builds an application with opal, however as srpt is missing build fails, both headers and libs...Options: 1. Make explicit Build-Depends: libsrtp-dev, then it is expected that all .debs will include depends, and when the package above are installed they srtp deps will be pulled in. packages are working as expected... 2. Make explicit Build-Conflicts: libsrtp-dev, then it is expected that all .debs will not depend on srtp. If a user wants to include srtp support, then they need to change the package configuration and we can claim it is unsupported.
A slight clarification (or correct me if in fact you meant something else, Mark):
Option 1: Have _source_ package build-depend on AND _binary_ *-dev package _depend_ on libsrtp-dev. And do this
Option 2) Have _source_ package build-conflict with libsrtp-dev.Since libsrtp only builds on some architectures, option 1 really means add those package relations only on relevant archs. The safest is then to build-conflict on negated list of supported archs, but if that feels too complex to handle, I guess that part can be skipped.
I recommend using d-shlibs to auto-resolve the binary relation!
Thus the recommend that we go for option 1.
I (obviously) agree, since that was the very point of packaging libsrtp :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
