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

Better file copy function #60

Closed
AaronO opened this issue Feb 23, 2014 · 1 comment
Closed

Better file copy function #60

AaronO opened this issue Feb 23, 2014 · 1 comment

Comments

@AaronO
Copy link

AaronO commented Feb 23, 2014

grunt's grunt.file.copy is slightly crippled due to the fact that it does not copy symbolic links but rather resolves them and then copies corresponding file.

For projects using many symlinks this can result in extremely large applications once built , hundreds of MBs for some simple node and html5 apps.

For these reasons, I think we should replace tasks/lib/utils.js:copyFile with a function that supports "copying" symlinks.

@steffenmllr
Copy link
Contributor

Isn't it intended behaviour to resolve symlimks when copying and packaging an app? Can you give me an example of an symlink that should be preserved instead of being copied?

@gabepaez gabepaez closed this as completed Aug 2, 2014
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

3 participants