Skip to content

multi: Remove non-root module replacements. #1599

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

Merged
merged 1 commit into from
Feb 9, 2019

Conversation

davecgh
Copy link
Member

@davecgh davecgh commented Feb 8, 2019

This modifies all of the modules, with the exception of the root module, to remove all replacement directives from their go.mod files files and update the requirements and module sums accordingly.

While it is nice to be able to build and test directly from each module directory and have it pull in the latest untagged changes when developing, having all of the overrides in each module makes it infeasible to use the module tools to help maintain the modules and thus makes it quite difficult to ensure they are all independently accurate for external consumers.

By maintaining all of the overrides in the root module and invoking all builds and tests from it, the overrides will apply to ensure the latest code is being built and tested.

This also modifies the tests script used with in CI to run all of the tests from the root module accordingly.

@davecgh davecgh added this to the 1.5.0 milestone Feb 8, 2019
@davecgh davecgh force-pushed the multi_remove_module_overrides branch 2 times, most recently from 3c6c6c3 to 6475eda Compare February 8, 2019 10:58

Verified

This commit was signed with the committer’s verified signature.
davecgh Dave Collins
This modifies all of the modules, with the exception of the root module,
to remove all replacement directives from their go.mod files and update
the requirements and module sums accordingly.

While it is nice to be able to build and test directly from each module
directory and have it pull in the latest untagged changes when
developing, having all of the overrides in each module makes it
infeasible to use the module tools to help maintain the modules and thus
makes it quite difficult to ensure they are all independently accurate
for external consumers.

By maintaining all of the overrides in the root module and invoking all
builds and tests from it, the overrides will apply to ensure the latest
code is being built and tested.

This also modifies the tests script used with in CI to run all of the
tests from the root module accordingly.
@davecgh davecgh force-pushed the multi_remove_module_overrides branch from 6475eda to e052b9c Compare February 9, 2019 00:02
@davecgh davecgh merged commit e052b9c into decred:master Feb 9, 2019
@davecgh davecgh deleted the multi_remove_module_overrides branch February 9, 2019 01:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants