20.10.2015 10:07, Michael Tokarev wrote: > Control: tag -1 + confirmed pending > > 20.10.2015 09:31, Julien Cristau wrote: >> Control: reassign -1 libspice-server-dev 0.12.6-2 >> >> Not our bug, as the error message says this is an issue with the package >> providing spice-server.pc. > >>> configure: error: Package requirements (spice-server >= 0.6.3) were not met: >>> >>> Package 'libcacard', required by 'spice-server', not found > > Oh. This is the dependencies. libspice-server-dev should depend > on libcacard-dev. Will upload a new version asap.
Uploaded, but I really wonder. I remember thinking about this a bit when adding cacard support to spice debian package, but haven't realized the prob with .pc files (which might be artifical actually). The thing is: libspice-server1 iself depends on libcacard0, but none of the users of libspice-server1 should be aware of that, unless they use libcacard internally too. libspice-server-dev .h files don't include any of libcacard header files. The only place where libcacard is mentioned in libspice-server-dev is this .pc file, so pkgconfig checks for the corresponding libcacard.pc file which is in -dev package. While no other tools do that, eg, linker will happily find libcacard0.so.0 when linking with libspice-server.so. Should we really add this dependency? It sounds better to remove this requiriment from the libspice-server's .pc file than to add a dep. (In this particular case it is not important at all, one tiny extra dependency for these large packages is nothing. But I'm thinking about general rule here) Thanks, /mjt
