-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated build instructions #1108
Conversation
I suggest a different approach based on |
zonemaster/zonemaster-ldns#158 will not replace this PR, but if that is merged then it will be enough to run |
718ce02
to
561276b
Compare
@pnax, please review. |
@@ -36,14 +36,15 @@ the `develop` branch and that your clone is up-to-date. | |||
git fetch --all | |||
git branch | |||
|
|||
For Zonemaster-LDNS only - reset submodule (LDNS): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For information, it's more an update of the submodule than a reset (the submodule is checked out to the right commit).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected. Please re-review.
Purpose
This applies for the build instructions for Zonemaster-LDNS. That repository has a submodule to LDNS. If the submodule is checked out and the version is changed in the branch checked out, then then submodule must be updated. If changing between branches with different version of the submodule, then the submodule must also be updated.
The changes in this PR assumes that zonemaster/zonemaster-ldns#158 is merged.
How to test this PR
Review and test using the documents.