Hello Dominic, Thank you for coming back to this. On Tue 01 Jan 2019 at 06:41pm GMT, Dominic Hargreaves wrote: > -If a relationship field has a version number attached, only real > -packages will be considered to see whether the relationship is satisfied > -(or the prohibition violated, for a conflict or breakage). In other > -words, if a version number is specified, this is a request to ignore all > -``Provides`` for that package name and consider only real packages. The > -package manager will assume that a package providing that virtual > -package is not of the "right" version. A ``Provides`` field may not > -contain version numbers, and the version number of the concrete package > -which provides a particular virtual package will not be considered when > -considering a dependency on or conflict with the virtual package name. > -[#]_ > +A ``Provides`` field may contain version numbers, and the version number > +of the concrete package which provides a particular virtual package will > +be considered when considering a dependency on or conflict with the > +virtual package name. [#]_ It might be useful to have an example here to explain the sense in which the version number of the concrete package will be considered. As someone who has not had to think through a case of versioned Provides for any of his packages, it is hard for me to understand how versioned Provides works in even very general terms from this text. By contrast, the text you are replacing has a lot more details and is easy to understand. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature