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. Thus the recommend that we go for option 1. Mark
signature.asc
Description: This is a digitally signed message part.
