-
Notifications
You must be signed in to change notification settings - Fork 139
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
Option to skip outermost directory entry in cptofs #297
Comments
I'm willing to write a PR to fix this but am not sure of how best to do it without changing the general shape of the directory traversal code. Open to suggestions if anyone more familiar with the code can see a trivial fix 😄 |
I can see a not-terribly-shitty way to do it by adding a boolean parameter to |
#298 sort of addresses this by letting me write |
@copumpkin I think this is the correct behavior, cp -r does the same. |
@tavip not quite though: if I call |
Perhaps that's just a darwin thing though? http://serverfault.com/questions/11518/recursive-cp-copies-folder-contents-instead-of-folder-on-os-x |
I think so since on my Linux machine cp -r foo dest and cp -r foo/ dest both copy the folder. |
I see. That's probably more sensible either way. Now that we support multiple source arguments, this issue should be roughly equivalent to using |
Given my last ticket #296, I decided to instead copy my target filesystem into a temporary folder and then bulk
cptofs
from that temporary folder into the root of the target image. Unfortunately,cptofs
insists (as far as I could tell) on putting the outermost directory in the root. So for example if I create$TMP/target-root
and then putbin
,etc
, and so on into there. Then callingcptofs ... $TMP/target-root /
will put everything into/target-root
, which isn't what I want.The text was updated successfully, but these errors were encountered: