Re: Semantics of version number of a virtual package?

[Ian Jackson <ian@chiark.chu.cam.ac.uk>]

Warwick HARVEY writes ("Semantics of version number of a virtual package?"):
...
> What does it mean here that svgalib1 conflicts with svgalib <= 1.28-2?  Does
> it mean it conflicts with aout-svgalib <= 1.28-2?  Should this be allowed?
> Obviously it makes no sense to refer to, say, mail-transport-agent <= 5.3,
> but is it reasonable for backward-compatibility packages or should it be
> flagged as an error?

Dependencies with version qualifications are never matched by virtual
packages (ie, Provides).

If it did do anything it would compare with an optional version number
in the Provides, but this is not currently supported and is unlikely
to be soon if at all.

Ian.