[Flow] Composer question regarding Flow

[Christian Loock]

Am 04.11.2014 um 09:39 schrieb Karsten Dambekalns:
> Hi Martin.
>
> On 15.10.2014, at 20:59, Martin Kutschker <masi-20l4 at typo3.org> wrote:
>> 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.
> Flow requires migrations, see https://git.typo3.org/Packages/TYPO3.Flow.git/blob/HEAD:/composer.json
>
> And it requires it as dev-master. Now, if you root manifest does not declare dev as an “allowed” stability, you must explicitly declare that dev is ok for the migrations package, and you can only do that in the root manifest. Just having "doctrine/migrations": “@dev” would not pull that package in, it’s just giving the stability flag. So it’s a combination of both at work here. If migrations ever go stable, that extra flag won’t be needed anymore.
>
>> I don't understand why typo3/flow requires typo3/fluid, typo3/eel and typo3/party. Why is it supposed that I will need them?
> Because Eel is used in parts of the configuration, so you can use Eel expressions in settings. Party and Fluid would be up for discussion, though. But we’ve been there in Berlin… OTOH, why would you not want to use Fluid? ;)
IIRC, typo3/party is somewhat directly integrated into flows account 
model. Security probably wouldn't work without it.

If a package has dependencies, they are probably there for a reason. I 
dont know why you would even bother with removing them.

>
> Regards,
> Karsten
>
>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow