Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modman link --copy question/issue #51

Open
strelok opened this issue Nov 29, 2013 · 2 comments
Open

modman link --copy question/issue #51

strelok opened this issue Nov 29, 2013 · 2 comments

Comments

@strelok
Copy link

strelok commented Nov 29, 2013

  1. run "modman link --copy Testmodule"
  2. run "modman deploy-all" and you got:
CONFLICT: directory already exists and is not a symlink:
 app/code/local/Vendor/Testmodule/* app/code/local/Vendor/Testmodule/
(Run with --force to force removal of existing files and directories.)
Error occurred while deploying 'testmodule'.

Deployed all modules with 0 errors.

So my question is how I should deploy module changes correctly in this case?
logical that if the module was "installed" with flag "--copy" it should be also "copied" after "deploy" command.
I just want to get rid of symlinks! :)

p.s. Message "Deployed all modules with 0 errors" seems incorrect, because there was an error :)

@colinmollenhour
Copy link
Owner

I had not intended people use the --copy on an ongoing basis, more as a one-time use tool for example to create zip archives for distribution. However you should be able to use "modman deploy-all --copy" for example.

@strelok
Copy link
Author

strelok commented Dec 3, 2013

seems like "modman deploy-all --copy" ignore "--copy" and same "conflict" occurs :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants