starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 05:16:00 +03:00

[GH-ISSUE #1270] Document mime types depenency #684

New issue

Closed

opened 2026-03-04 01:47:51 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 01:47:51 +03:00

Owner

Originally created by @gaul on GitHub (Apr 14, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1270

Someone on StackOverflow recently asked about the mime types dependency:

https://stackoverflow.com/questions/61207571/s3fs-could-not-load-mime-types-for-curl-library/61208047#61208047

Should this be a hard dependency? Instead we could just warn about its absence since most users not require Content-Type.

Originally created by @gaul on GitHub (Apr 14, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1270 Someone on StackOverflow recently asked about the mime types dependency: https://stackoverflow.com/questions/61207571/s3fs-could-not-load-mime-types-for-curl-library/61208047#61208047 Should this be a hard dependency? Instead we could just warn about its absence since most users not require Content-Type.

kerem closed this issue

2026-03-04 01:47:51 +03:00

kerem commented

2026-03-04 01:47:52 +03:00

Author

Owner

@ggtakec commented on GitHub (Apr 14, 2020):

https://github.com/s3fs-fuse/s3fs-fuse/blob/master/COMPILATION.md and https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#qwhat-do-i-need-to-know have a brief explanation.

However, it does not explain the required packages for each OS.
(Note that the package containing mime.types(mailcap) is not included in the dependency of the s3fs package and is an environmental problem.)

So, I would like to consider whether the recommended packages for each OS should be prepared in any of the documents.

@ggtakec commented on GitHub (Apr 14, 2020): https://github.com/s3fs-fuse/s3fs-fuse/blob/master/COMPILATION.md and https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#qwhat-do-i-need-to-know have a brief explanation. However, it does not explain the required packages for each OS. (Note that the package containing mime.types(mailcap) is not included in the dependency of the s3fs package and is an environmental problem.) So, I would like to consider whether the recommended packages for each OS should be prepared in any of the documents.

kerem commented

2026-03-04 01:47:52 +03:00

Author

Owner

@juliogonzalez commented on GitHub (Apr 16, 2020):

Should this be a hard dependency? Instead we could just warn about its absence since most users not require Content-Type.

Just so you know: on Debian, openSUSE/SLE and Fedora/EPEL the packages providing the mime types config file are Requires. So for the packages on the distributions, this is a runtime hard dependency (Debian had it, openSUSE/SLE had it, so I just did the same for Fedora/EPEL).

Also I am not 100% sure most users don't need it. I think most users have the file and they just don't know. Without it, any application using MIME will be confused. And as the MIME type is not defined during upload, and you never know who will be reading files from the bucket... that could be a problem.

But I admit I am not an expert on this area.

https://github.com/s3fs-fuse/s3fs-fuse/blob/master/COMPILATION.md and https://github.com/s3fs- fuse/s3fs-fuse/wiki/FAQ#qwhat-do-i-need-to-know have a brief explanation.

Which FMPOV is OK. We don't tell the packages in other cases. Only the dependencies in terms of software that needs to be available.

However, it does not explain the required packages for each OS.

Those packages are already at https://github.com/s3fs-fuse/s3fs-fuse/wiki/Installation-Notes and it seems they are right for all the Linux Distributions listed there (mime-support for Debian and Ubuntu, mailcap for RHEL/CentOS/Fedora and nothing for openSUSE/SLE (as it's part of the base system as part of aaa-base package)).

@juliogonzalez commented on GitHub (Apr 16, 2020): > Should this be a hard dependency? Instead we could just warn about its absence since most users not require Content-Type. Just so you know: on Debian, openSUSE/SLE and Fedora/EPEL the packages providing the mime types config file are `Requires`. So for the packages on the distributions, this is a runtime hard dependency (Debian had it, openSUSE/SLE had it, so I just did the same for Fedora/EPEL). Also I am not 100% sure most users don't need it. I think most users *have* the file and they just don't know. Without it, any application using MIME will be confused. And as the MIME type is not defined during upload, and you never know who will be reading files from the bucket... that could be a problem. But I admit I am not an expert on this area. > https://github.com/s3fs-fuse/s3fs-fuse/blob/master/COMPILATION.md and https://github.com/s3fs- fuse/s3fs-fuse/wiki/FAQ#qwhat-do-i-need-to-know have a brief explanation. Which FMPOV is OK. We don't tell the packages in other cases. Only the dependencies in terms of software that needs to be available. > However, it does not explain the required packages for each OS. Those packages are already at https://github.com/s3fs-fuse/s3fs-fuse/wiki/Installation-Notes and it seems they are right for all the Linux Distributions listed there (`mime-support` for Debian and Ubuntu, `mailcap` for RHEL/CentOS/Fedora and nothing for openSUSE/SLE (as it's part of the base system as part of `aaa-base` package)).

kerem commented

2026-03-04 01:47:52 +03:00

Author

Owner

@gaul commented on GitHub (Apr 18, 2020):

I think packages should either require or recommend mime-types and the compilation instructions should suggest it but if the file is missing at run-time s3fs should warn once about this and continue.

@gaul commented on GitHub (Apr 18, 2020): I think packages should either require or recommend mime-types and the compilation instructions should suggest it but if the file is missing at run-time s3fs should warn once about this and continue.

kerem commented

2026-03-04 01:47:52 +03:00

Author

Owner

@ggtakec commented on GitHub (Apr 18, 2020):

The mime.types file is not needed when building s3fs, but it is only needed at runtime.
On current master, if the mime.types file does not exist, an error is output and s3fs cannot start.
Should I output this message with a little more detail?

@ggtakec commented on GitHub (Apr 18, 2020): The mime.types file is not needed when building s3fs, but it is only needed at runtime. On current master, if the mime.types file does not exist, an error is output and s3fs cannot start. Should I output this message with a little more detail?

kerem commented

2026-03-04 01:47:52 +03:00

Author

Owner

@gaul commented on GitHub (Apr 29, 2020):

The StackOverflow answer has attracted several votes and I suspect this new requirement is breaking users who compile master from source.

@gaul commented on GitHub (Apr 29, 2020): The StackOverflow answer has attracted several votes and I suspect this new requirement is breaking users who compile master from source.

kerem referenced this issue

2026-03-04 02:01:16 +03:00

[PR #684] [MERGED] Correct signedness warning #1604