Feature #54151

Implement proper package dependency handling

Added by Markus Klein almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-12-02
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

Hi!

For TYPO3.CMS I reimplemented the dependency handling of the PackageManager. #52828

These two concepts were used in the patch:

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

Related to TYPO3 Core - Bug #52828: extTables cache file creation does not respect extension orderClosed2013-10-15

Actions
Related to TYPO3.Flow - Bug #50088: Loading order of packages does in some cases not respect depenenciesResolved2013-07-16

Actions
Related to TYPO3.Flow - Feature #30418: Package bootstrapping following dependenciesNew2011-09-29

Actions
#1

Updated by Christopher Hlubek over 7 years 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 7 years 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.

Also available in: Atom PDF