Feature #54151
Implement proper package dependency handling
| Status: | Resolved | Start date: | 2013-12-02 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: | No |
Description
Hi!
For TYPO3.CMS I reimplemented the dependency handling of the PackageManager. #52828
These two concepts were used in the patch:
- http://en.wikipedia.org/wiki/Dependency_graph
- http://en.wikipedia.org/wiki/Topological_sorting (Algo by Kahn (1962))
Besides that the CMS patch contains some extra logic to include system extension always first. This specific part will not be necessary for Flow.
Please judge on your own, if you'd like to have this implementation in Flow as well.
Related issues
History
#1 Updated by Christopher Hlubek over 1 year ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Hi Markus,
thanks for the hint. We implemented it using the mentioned algorithm at the Neos code sprint in Nürnberg and the change is merged in Flow master.
#2 Updated by Markus Klein over 1 year ago
Hi!
Very nice. I hope you saw that Tom and recently refactored that a bit and extracted that logic into a separate class in CMS. So the functionality is now nicely decoupled.