-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
Copying metadata between FS objects #409
Comments
I think the issue here is actually coming from the If you look at the implementation of |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I'm looking for a way to copy/mirror data from
ReadTarFS
toOSFS
. Everything works fine unless the archive contains symlinks. All copy/mirror methods are implemented viacopy_file_internal
function which in turn callsopenbin
method of appropriate FS-inherited object. And inReadTarFS
implementation ofopenbin
there isI get why this check is there - the library strives to be a lowest common denominator for different filesystems and symlinks are not universally-supported. I believe that my current issue can be solved by patching
if not member.isfile()
toif not (member.isfile() or member.issym())
and usingfs.copy.copy_fs
withon_copy
callback to alter metadata withsetinfo
call (as symlinks are simply text files with magic attribute set on them).But it feels that a more general problem lurks there. Currently there is no sane way to customize copying (of both data and metadata) for cases when both filesystems actually support the same set of features and thus it's safe to copy some exotic types of files (like symlinks/sockets/devices/... in tar and ext4).
I like the idea behind this library but lack of such feature makes it unusable for my case. Off the top of my head I can think of one solution. What do you think about it?
PS: Thanks for your time and for an interesting piece of software! =)
The text was updated successfully, but these errors were encountered: