Add the possibility back files to repository

[vdubyna]

Symlinks are not very useful in some cases as they do not work correct with __DIR__ and __FILE__ constants.

I suggest to add possibility to do reverse copy from the project to the vendor dir.

[Vinai]

What would be the intended scenario?

• Deploy using copy from vendor/ package dir
• Develop within the Magento source tree
• Copy from Magento source tree back to vendor/ package dir

Is that right? I can see the use for that. I think it would be best to create a command based on https://github.com/magento-hackathon/composer-command-integrator since this isn't really composer installer related.

[vdubyna]

Yes, that is right. It should be feature for developers. And the command line is what we need.
I've got some problems with https://github.com/magento-hackathon/composer-command-integrator
I'll add my proposals there too, but in a couple of days.

[Flyingmana]

should be not so hard to achieve. nearly all of the code of MagentoHackathon\Composer\Magento\Command\DeployCommand can get reused.
I dont belive that simple switching the key/value of the mapping is enough, so we also need a extra deploystrategy similar to our copy.php which reverses the copy function in this line https://github.com/magento-hackathon/magento-composer-installer/blob/master/src/MagentoHackathon/Composer/Magento/Deploystrategy/Copy.php#L73

Anyone a suggestion how we can do this in a semantic correct way without copy the half code of both files?
I think about extracting the copy call into an own class method and simple extend from the copy.php so only one method needs to get overwritten. Same for the DeployCommand and the getDeployStrategy call.

Semantically not so good, but it would minimize the code which needs to get maintained.

[amenk]

On which modules does that cause problems? I basically like to have everything in vendor and now where else. I install using "composer.phar --prefer-source" so I have direct access to the upstream GIT repos and can make pull requests and so on.