Feature proposal #4736
open
Implement version dependency
Added by krileon about 10 years ago.
Updated over 7 years ago.
Start date:
19 September 2014
Description
Currently you can have package dependency, but you can't have package version dependency. This is helpful to have modules, plugins, etc.. depend on a component version for example. Extend the dependency feature.
- Target version set to 5.0.0
- Status changed from Assigned to Rejected
- Target version deleted (
5.0.0)
- % Done changed from 0 to 100
There's no way to reliably do. Versions are dynamically parsed on package rendering. The versions can change at any time as it's due to the available files. Versions would have to be done entirely different and likely require too much manual configuration on every update.
- Status changed from Rejected to Assigned
- Target version set to 6.0.0
- % Done changed from 100 to 0
This can be done using a Repeat usage. It should output as follows.
Version - Operator - Package - Version
So you could have the following.
1.0 <= CB 1.5
Meaning version 1.0 requires CB 1.5 or older and will package it with it. The operator may not even be needed though. Few more examples as follows.
Latest = CB Latest
Nightly = CB Latest
Beta = CB Nightly
- Target version changed from 6.0.0 to 8.0.0
Also available in: Atom
PDF
Updated by