-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
archive/tar: add (*Writer).AddFS #58000
Comments
CC @dsnet |
Generally speaking we keep archive/tar and archive/zip with comparable API, so I think it makes sense to accept this at the same time we accept the archive/zip change. |
I thought I needed this function in a program I was writing, so I wrote it (I've since changed my mind about needing it in this case). Should be something like this.
|
Based on the discussion above, this proposal seems like a likely accept. |
No change in consensus, so accepted. 🎉 |
The method AddFS can be used to add the contents of a fs.FS filesystem to a tar archive. This method walks the directory tree starting at the root of the filesystem and adds each file to the archive. Fixes: golang#58000
The method AddFS can be used to add the contents of a fs.FS filesystem to a tar archive. This method walks the directory tree starting at the root of the filesystem and adds each file to the archive. Fixes: golang#58000
Change https://go.dev/cl/513316 mentions this issue: |
The method AddFS can be used to add the contents of a fs.FS filesystem to a tar archive. This method walks the directory tree starting at the root of the filesystem and adds each file to the archive. Fixes: golang#58000
The method AddFS can be used to add the contents of a fs.FS filesystem to a tar archive. This method walks the directory tree starting at the root of the filesystem and adds each file to the archive. Fixes: golang#58000
This proposal is similar to #54898, except for
archive/tar
.The idea would be to provide an
AddFS
method that would tar an entire directory tree provided byfs.FS
.Why implement this:
archive/zip
, it makes sense to implement it forarchive/tar
since the use case is similar.fs.FS
exists, we might as well use it.The text was updated successfully, but these errors were encountered: