Project

General

Profile

Actions

Feature proposal #4736

open

Implement version dependency

Added by krileon over 6 years ago. Updated almost 4 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
Target version:
Start date:
19 September 2014
Due date:
% Done:

0%

Estimated time:

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.

Actions #1

Updated by krileon over 5 years ago

  • Target version set to 5.0.0
Actions #2

Updated by krileon over 5 years ago

  • 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.

Actions #3

Updated by krileon over 5 years ago

  • 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

Actions #4

Updated by krileon almost 4 years ago

  • Target version changed from 6.0.0 to 7.0.0
Actions

Also available in: Atom PDF