[Flow] Broken 'Flow\Composer feature' to copy packages files into installation on composer install?

[Karsten Dambekalns]

Hi.

On 16.07.2014, at 02:31, Stefan Reichelt <eichelt at web.de> wrote:
> [* I think Neos's usage of that feature might be obsolete since
> 'typo3/neos-base-distribution' already contains all files the typo3/neos
> package wants to copy?]

That is probably because we *want* to put different versions in place - there is a distinction between “Defaults” and “Essentials” when those files are copied.

> So yeah, might this thing be a bug and should I create an issue for it
> or do I did I do it wrong and/or have something misconfigured in my
> installation?

Sounds like a bug, so feel free to open an issue!

> Also, is there no documentation about this particular feature or did I
> miss it somewhere? :(

No, not documented. Also the concept has it’s flaws still, e.g. there is no order to be set, so if you want some defaults to apply for a file that Flow itself already copies, there isn’t a way to make sure the right one wins. That’s part of the reason it’s not documented so far: "fear of widespread adoption” ;)

Regards,
Karsten