[Question] Why differentiate copy-from-recipe and copy-from-package?

[javiereguiluz]

At first I thought that recipes were just manifest.json files at the project's root dir. But then we have two separate configurators to copy contents from packages and recipes.

My questions:

• Why can't we have only copy-from-package?
• Where are the recipes stored?
• Can the community create their own recipes? If so, where will they store the contents? (I guess that in the same Composer package, so why is copy-from-recipe needed?
• Where are the "core recipes" stored? For example, will the framework-bundle recipe be stored publicly on https://github.com/symfony/symfony/tree/master/src/Symfony/Bundle/FrameworkBundle or privately on Flex servers? At first I thought that Flex servers would only take care of curating dependencies, managing the aliases defined, etc.

[fabpot]

That's a lot of questions.

• copy-from-recipe is sometimes needed to integrate packages that are not meant to work with Symfony out of the box (see sensiolabs/security-checker for an example where creating a bundle would be overkill)

• The recipes are not "stored" on the client, but served by https://flex.symfony.com/. There is a local HTTP cache under ~/.composer/ though.

• No, recipes cannot be part of the package contents, but should be hosted on a specific recipes repository. At first, there is only one, but we will support having several ones.

• Same as the previous one. Recipes are stored independently of the packages.