Add 'man' target to build the MAN pages#7637
Conversation
|
Thanks for your pull request, @wilzbach! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. |
src/posix.mak
Outdated
| # cxx-unittest Check conformance of the C++ headers | ||
| # build-examples Build DMD as library examples | ||
| # clean Remove all generated files | ||
| # man Build the MAN pages |
There was a problem hiding this comment.
nit: "Generate the man pages" as that is the text used in the comment below.
3af734c to
6c5d542
Compare
|
Is it possible to add a test for this to our CIs? I'm thinking something simple that generates the man page and then verifies that the file actually contains something sane. I'm also worried that this can get broken somehow, and we'd only know about it after the release when one of our maintainers tries to create their package, or worse one of the users opens a man page with nothing or nonsense in it. UPDATE: Or perhaps add the output to CyberShadow/DAutoTest |
FYI: by adding it to the
Yep, excellent idea: dlang/dlang.org#2067 |
|
As dlang/dlang.org#2067 is in, I rebased this PR and now we should see the changes on DAutoTest. |
7f8b48e to
efd1bec
Compare
|
So it turns out that dlang/dlang.org#2067 broke DAutoTest (sorry @CyberShadow) because we modify versioned files. |
|
Great it seems like the vibe.d and dub testsuite depend on code.dlang.org being online. I wonder dub doesn't fallback to use its mirrors there. Anyhow this change doesn't even touch the compiler source code. and unbreaks DAutoTest |
Follow-up to dlang#7637 Not sure whether the nightlies depend on the exact path. CC @MartinNowak
We should be a bit careful here to avoid breaking the nightly builds.
CC other package maintainers: @Vild @jordisayol @WebDrake (who knows more?)
See also: #7507