-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Copy directory #32
Comments
Recursively? |
I hadnt thought about that. |
There are also two ways to handle this.
Option 2 is closer to the moban meaning of a Option 1 is closer to the moban meaning of a Option 1 is a way to automatically deploy new templates to the target without first updating the config. I feel option 2 is better/safer. It will be less usable/useful, as it can not be used where there are other files in the target, but it doesnt create new problems, like allowing two entries for the same target directory. Option 1 is a feature which should be planned more carefully, and also applied to templates. |
Option 2 has the benefit of being useful for enforcing 'empty' directories. |
With option 1, lazy copying is in place. If a file has been copied and no changes are found, the copying won't happen. So in a large tree of 100 files, initial run would cost 100 copies. In the next run, only delta changes is copied over and the costs could be: 0 - 100. With option 2: destination folder is removed. hence the cost is constant: first run is 100 copies and Nth run is 100 copies, in previous example. |
It looks like you did option 2. IMO option 2 should be The only syntax I can think of that is suitable for option 1 is |
Will address it |
released |
If a
copy
source is a directory, all files in it should be copied to the destination.The text was updated successfully, but these errors were encountered: