3 ms·
> Do users declare a dependency on "= 37", or ">= 37"? (Or do they have the option of either?) "= 37". > How do you push backwards-compatible changes like bug
by twic 8y ago
> Do users declare a dependency on "= 37", or ">= 37"? (Or do they have the option of either?)
"= 37".
> How do you push backwards-compatible changes like bugfixes? Is the rule that every new release is a new version number?
A backwards-compatible change gets a new version number, like any other change.
The system does actually let you use version numbers like "37.1", but it doesn't assign any meaning to them. They're all opaque symbols, really. You could just as well have versions "first", "new", "improved new", "new new", "new new (final)", "new 2", etc.
> If you do the >= thing, do you automatically take the newest compatible dependency or the oldest possible one (vgo-style)?
We don't use ">= 37".
> Do you run tests on reverse dependencies when dependencies are updated?
Oh god no.
Personally, when i'm upgrading a library, it will usually be to address a need of a particular consumer, and i will develop the upgrade and the change to the consumer in concert. So that's sort of testing it with a reverse dependency, but only one.
> Are you allowed to have diamond dependencies, e.g., A depends on B and C, B depends on AdminTools 37, and C depends on AdminTools 38?
You can express a dependency like that, and if there is a conflict, the package manager shouts and you and stops. You then have to write something like "no really, use version 38" to persuade it to work.
> Do you resolve that with a single copy of AdminTools, or two?
A single copy.
To my mind, these are all questions about our package management tool, not our versioning scheme.