package-validator
package-validator copied to clipboard
Requirement: A .portable or .install dependency of the meta with no version boundary
Or the boundary is not strict enough.
The version dependency from a meta package should be either exact "[version]" or bounded based on the version of the meta package, e.g. 1.2.0 ~= "[1.2.0, 1.21)" - it allows for fixes up to the next version.
@ferventcoder milestone?
Can def be 0.1.0
@ferventcoder going to take a stab at this one tomorrow. Do you know how the bounded version translates into the parsed NuSpec information. Is that where the Minimum and Maximum versions come into play?
Not a clue mate.