mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #2421] Providing more details in docs #1192
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1192
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tuxpeople on GitHub (Feb 25, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2421
Hi
I'm stumbled upon this:
github.com/s3fs-fuse/s3fs-fuse@70a30d6e26/COMPILATION.md (L9-L23)Would it be possible to differentiate between build dependencies and runtime dependencies?
Thanks!
@ggtakec commented on GitHub (Apr 14, 2024):
@tuxpeople I'm sorry for my late replying.
Could you tell me specifically what you stumbled on?
@gaul commented on GitHub (Apr 14, 2024):
I believe he wants to separate build dependencies:
From runtime dependencies:
/etc/mime.typesas default regardless of the OS/etc/apache2/mime.typesif OS is macOSmimeoption without detecting these default filesAgree that this would be a slight improvement. It would also be good to clarify that OpenSSL is not required and that either GnuTLS or NSS can be used.
@ggtakec commented on GitHub (Apr 15, 2024):
@gaul Thanks for your comments.
I created PR #2445, please check it.
@tuxpeople commented on GitHub (Apr 18, 2024):
No worries, I've got the same problem with issues people open in my repos ;-)
Yes. Unfortunately, I'm unable to remember why exactly I asked for this. I think I've tried to create a container image with it, and my goal was to have a small footprint using a multi-stage build.
Anyway, the PR looks good to me, thanks a lot!
@ggtakec commented on GitHub (Apr 28, 2024):
@tuxpeople Thank you for the reply.
I merged PR#2445.
If there are any parts that are still unclear, please let us know.
(This PR will be closed.)