-
Notifications
You must be signed in to change notification settings - Fork 23
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
Document the examples, including Docker instructions; add BUILDING.md, update all READMEs #92
Conversation
@codeboten deserves a bunch of credit for eliminating module inconsistencies in our dependencies! 🥳 |
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.
Waou very nice PR!
Thank you both. This PR is just what we needed to be able to open/launch this project to a wider audience! |
Co-authored-by: Laurent Quérel <laurent.querel@gmail.com>
This trims the dependencies of the core modules. It's been on my wishlist forever! Note in particular the obfuscation processor has some wild dependencies and I don't want them in production. No issue was filed about this, we were just stuck with all the Go module problems and doing the best we could until #92 introduced the `go.work` file now used. This PR was going to be only go.mod changes, but I observed a pre-existing test failure. Part of #96.
Noticed some bugs in the recent changes from #92, fixed here.
This PR (at last!) fixes a number of outstanding Golang module issues. We now use a checked-in go.work file.
The important aspect of this change, for the go.work approach to work, involves using the OTC
builder
with its--skip-get-modules
flag set. This allows the go.work file to be used instead, and we now callgo work sync
instead.There are no more
replace
statements in any of the go.mod files, so single-line commands will now work (after the next release).The new BUILDING.md instructions explains how to build either with a local Golang toolchain, or using a Docker Golang toolchain. Each example has been tested and updated for a number of minor changes, including:
printer
example (now with fewer dependencies)Fixes #72.