[Flow] Composer question regarding Flow

[Christian Loock]

If flow would require the migrations, composer wouldnt try to install them.

Fluid is the template engine flow uses. Typo3/party is used to store user
data in flows account management. Usually, if packages defined
depdendencies, they are there for a reason. It's good that you want to know
what they are used for, but this all explains itself when you work your way
through the docs.

Cheers

2014-10-15 20:59 GMT+02:00 Martin Kutschker <masi-20l4 at typo3.org>:

> Am 15.10.2014 20:47, schrieb Christian Loock:
>
>> The easiest way to get a working installation of a flow project with all
>> prequesites you need is to just do it as it says in the manual:
>>
>> composer create-project --dev --keep-vcs typo3/flow-base-distribution
>> tutorial 2.0.0
>>
>
> That would be too easy :)
>
> I deliberatedly tried different ways to get a feel for the dependencies.
>
> If you look at typo3/flow-base-distribution you'll notice that it requires
> "doctrine/migrations": "@dev". Which typo3/flow OTOH does not. So that's
> why it breaks. IMHO this is a bug.
>
> Masi
>
> PS:
>
> I don't understand why typo3/flow requires typo3/fluid, typo3/eel and
> typo3/party. Why is it supposed that I will need them?
>
>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>