[Pkg-clamav-devel] bug #500416

[Luk Claes]

Michael Tautschnig wrote:
>> This one time, at band camp, Michael Meskes said:
>>> On Sun, Sep 28, 2008 at 08:09:15PM +0100, Stephen Gran wrote:
>>>> release.  clamav-daemon probably needs to be more closely coupled to it
>>>> in terms of versioned dependencies, but I'm having a hard time figuring
>>>> out how to do it in an automated manner.  We can of course do something
>>>> like:
>>>>
>>>> Depends: clamav-base >=(0.94)
>>>> Conflicts: clamav-base (0.95)
>>>>
>>>> and then increment the numbers with each release, but that feels really
>>>> fragile to me.
>>> Is there a reason to not use a dependency on "clamav-base (= ${binary:Version})"?
>> Doesn't that break binNMU's?  Maybe that's ok, but that was why I
>> changed it away from a strict = at some point.  I could be wrong, and I
>> could also be being cautious when I don't need to.
> 
> AFAIK ${binary:Version} is ok, ${source:Version} was the variable one shouldn't
> use.

I guess the doubts come from ${source-Version} which behaved quite
differently...

In general it depends:

          |    Arch: any       |   Arch:all
----------+--------------------+---------------
Arch: any |  binary:Version    | source:Version
Arch: all |  >= source:Version | source:Version

So 'Arch: any' package should depend on 'source:Version of Arch: all'
package, 'Arch: all' should depend on '>= source:Version of Arch: any'
package to be binNMU safe.

The above is of course only true if a rather strict version is needed.

So clamav-daemon should depend on the source:Version of clamav-base.

Cheers

Luk