Definition of loading-order for Packages/TypoScripts

Using Neos & Flow
4

hi @mficzel,
my problem with the loading-order is solved by @aertmann. Seems not to be a problem of «my» abstraction package «base-neos-distribution» and wrong loading-sequence. Rather the bug https://jira.neos.io/browse/NEOS-1821 has plagued me.

Thank you for your help.
For better understanding and to summarize as a real-life example for other seekers:

  • Is «a dependency» synonymous for «use of require» in composer.json? Can’t find the term dependency while overflying the composer-docu.

If yes, would it mean: if I would like to include my package «base-neos-distribution» and the typoscript within (aka Neos-Website «Vendor.Site») after the «typo3/neos-seo»-package:

I have to «require» the ***«neos-seo»***-package in my Neos-Website «Vendor.Site» like this:

//Vendor.Site/composer.json
{
    "name": "cleanAndClear/base-neos-distribution",
    "type": "typo3-flow-site",
    "description": "Clean Neos Base Distribution",
    "require": {
         "typo3/neos-seo": "~1.0",        
}
  • Right summary or do I have misunderstood the therm dependency and your explanation?