On Tue, 9 Dec 2008 10:02:25 +0000 (UTC) Andy Hawkins <[EMAIL PROTECTED]> wrote:
> I'm in the process of building my first package. Most of the
> dependencies generated by ${shlibs:Depends} are fine for the package,
> but I need to force the version of one particular component.
This "component" is a shared library and therefore a build dependency.
If you are going to force a particular version, you should do it in
Build-Depends.
dpkg-shlibdeps will then work out the rest using any symbols files that
may exist.
But you also need to answer Paul's question - why are you doing this?
If your package needs >= 1.2.1 (and there should be spaces in that
string) then it check for that version during the build. IIRC you then
put the string before shlib:Depends -
e.g. for one of my upstream projects (not yet in Debian)
Depends: libestron0 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
That is a different use case - where the Depends is added to an
internal package to ensure that both are upgraded together. (Policy 8.5)
> 1. Is this an acceptable method of listing the required libraries, or
> should I list all of them individually?
No - extra depends on debian/control should be those that are not
calculated by shlib:Depends. You cannot replace shlib:Depends with a
fixed list.
> 2. If this is acceptable, will having two 'dependencies' make it do
> the right thing?
No.
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgpHeMWYVxPhc.pgp
Description: PGP signature
