-
Notifications
You must be signed in to change notification settings - Fork 0
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
remove every language we don't care about #15
Conversation
this actually ends up making our upgrade story significantly easier. i already have a branch on Bazel 0.26.x |
|
||
load("//ruby:rules.bzl", "ruby_proto_repositories") | ||
|
||
ruby_proto_repositories() |
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.
😢
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.
i know :'(
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.
👍 just curious, do you know what the blockers have been for us using go_proto_library
from rules_go
?
@akakitani iirc, relevant issue: golang/protobuf#547 |
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.
Wonderful, thanks!
I got sick of trying to make all the languages we don't actually use work... so I deleted everything except for closure, go, and gogo (maybe we might experiment with it one day!?).
This should make the footprint a lot smaller and maintenance a lot easier in the future.
Should we ever care for using one of those languages for protobuf, we shouldn't use rules_protobuf anyways in favor of whatever is the native Bazel rules.
build passed in: https://travis-ci.org/vsco/rules_protobuf/jobs/587324241