Story #939
Switch between package versions
| Status: | Accepted | Start date: | ||
|---|---|---|---|---|
| Priority: | -- undefined -- | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Package Manager | Spent time: | - | |
| Target version: | Sprint #0 | Estimated time: | 0.00 hour | |
| Votes: | 0 |
Description
A system administrator can switch between different versions of installed packages.
Note:
The package manager should avoid downloading packages more than once
History
Updated by Robert Lemke almost 5 years ago
- Priority changed from Must have to -- undefined --
- Target version set to Sprint #0
Updated by Christopher Hlubek over 4 years ago
This has to be discussed as stated in http://forge.typo3.org/attachments/445/08.txt
For storing multiple versions of one package a lot of code must be touched.
Updated by Thomas Allmer about 4 years ago
Another approach might be
You have a Packages Subfolder for each Context.
The Priority of the Packages would be
1) Context
2) Local
3) Global
Example:
Packages\Global\Blog [v0.1]
Packages\Local\Blog [v0.2]
Packages\Development\Blog [v0.3]
While beeing in the Development Context I will use v0.3 of the Blog. In the Production Context I will use v0.2.
If I delete the Local\Blog Directory. My Development Context doesn't change; I'm still using v0.3. However in
Production Context I will now use v0.1
With this approach you can easily uses multiple Versions of Packages in different Context. [assuming the data structure didn't changed]
Packages | \- Global | | \-FLOW3 | | \-Fluid | | \- ... | \- Local | | \-FLOW3 | | \- ... | \- Development | | \-FLOW3 | | \- ... | \- YourContext | | \-FLOW3 | | \- ...
comments?