Use dh_mkdocs instead of symlinking static files manually#17
Open
mitya57 wants to merge 2 commits intoxtaran:masterfrom
Open
Use dh_mkdocs instead of symlinking static files manually#17mitya57 wants to merge 2 commits intoxtaran:masterfrom
mitya57 wants to merge 2 commits intoxtaran:masterfrom
Conversation
Owner
|
Whoa, cool! Will have a look. Thanks for the hint on |
Owner
|
JFTR: The Travis CI errors are not due to this pull-request but because something's broken with either perlbrew or (more likely) the current perl development branch as the installation of the latter already fails. They passed on all Perl versions except perl-dev and perl-bleed. |
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
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.
I have created a new helper tool, dh_mkdocs, which takes care of symlinking static files.
This pull request makes use of that tool instead of symlinking stuff manually. It is more future-proof: when mkdocs internal files change, only a rebuild will be needed to fix the links.