e2fsprogs: do not build fuse2fs #1687
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@MilhouseVH can you backport this too pls, else we'll forget for 8.2 |
|
Done. |
lrusak
approved these changes
Jun 14, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned on Slack, clean builds do not build and install the
fuse2fsbinary.However, if
e2fsprogsis ever rebuilt thenfuse2fswill be automatically enabled byconfigurewheneverfuse.his detected, and thenfuse2fswill be built and installed.fuse.his installed by thefusepackage which is built near the end of the build long aftere2fsprogs(it's needed byfuse-exfatin order to create the image).So a clean build will not include
fuse2fs, but a later incremental build that rebuildse2fsprogswill containfuse2fs.In order to remove this uncertainty from the build, this PR explicitly disables
fuse2fs.