-
Notifications
You must be signed in to change notification settings - Fork 46
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
Onomy enhancements #81
Conversation
If we want to handle this now, we should do something like export a |
This reverts commit 3395b38.
# Conflicts: # chains.yaml
# TODO: Heighliner will not produce working builds until https://github.com/onomyprotocol/onomy/pull/129 merged. | ||
# If PR not merged for your git-ref, then update and push to our fork, https://github.com/strangelove-ventures/onomy, with Onomy upstream. | ||
# And manually run heighliner command with `-o strangelove-ventures --git-ref main --tag <semver>`. | ||
build-target: make install |
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.
@agouin Decided to take this approach vs. a long build target.
As of this writing, onomyprotocol/onomy#129 has no activity from the Onomy team. I've reached out to them in our dedicated slack channel.
chains.yaml
Outdated
- name: onomy-gbt | ||
github-organization: onomyprotocol | ||
github-repo: arc | ||
dockerfile: rust |
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.
This will work but rust
is now deprecated. cargo
replaces it.
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.
Thanks, I missed that deprecation. I'll make a quick update.
Onomy