add feature to deply packages without own definition

[Flyingmana]

No description provided.

[razbakov]

is it for those which are not "type": "magento-module"?

[Flyingmana]

yes, I planned kind of a whiteliste for package names, so they the installer handles them ans they were magento-modules. I wonder if there would be needed much more at all, as we already have the magento-map-overwrite

[razbakov]

i mean all non-magento modules should be just moved to lib folder

[Flyingmana]

that would cause problem with people, who have a working composer setup.
Also nearly non php package would match the magento autoloading, causing possible odd sideeffects if accidentily a file path there matches the autoloading pattern.

[razbakov]

|- webroot
|  |- lib
|- vendor
|- composer.json

for example i want to use https://github.com/symfony/Process.
the problem is that only content of webroot folder should be synced to production.

how would you solve it?

[Flyingmana]

I see, thats what I build the libraryDeploy for, it copys typical composer packages into a separate directory (so no conflict with autoloading) and creates a autoload map for it. Its not documented yet and also not finalized for working automagically.
And also its not intended for magento modules, which is why we have this Issue here :)