build: fix rrsync manpage fallback#970
Merged
Merged
Conversation
tridge
approved these changes
Jun 6, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #868 by making
maybe-make-manderive fallback manpage names from the output basename rather than the markdown input path.When
--with-rrsyncis enabled and md2man cannot generate manpages,make mancallsmaybe-make-man support/rrsync.1.md. The generated and release manpage name isrrsync.1but the fallback path previously looked forsupport/rrsync.1. That missed the prebuilt release manpage and failed withERROR: support/rrsync.1 cannot be created.This keeps the existing fallback behaviour for top-level manpages and makes the support/rrsync path match the actual generated output name.