chore(man): Don't compress man pages during build #317
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
Compressing man pages is a distribution / user preference that should be handled on the packaging side of things. Indeed, compressing man pages by default imposes a compression algorithm / level for users whereas most package managers handle that already and allow users to choose / configure them (if wanted at all). Additionally, it can lead to unexpected side effects. For instance, gzip recording timestamps in metadata by default, which prevents reproducible builds (see 905f641). See https://cmpct.info/~sam/blog/posts/automatic-manpage-compression/ for detailed rational.
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.
Description
Compressing man pages is a distribution / user preference that should be handled on the packaging side of things.
Indeed, compressing man pages by default imposes a compression algorithm / level for users whereas most package managers handle that already and allow users to choose / configure them (if wanted at all). Additionally, it can lead to unexpected side effects. For instance, gzip recording timestamps in metadata by default, which prevents reproducible builds (see 905f641).
See https://cmpct.info/~sam/blog/posts/automatic-manpage-compression/ for detailed rational.