Skip to content
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

LOW: Consider publishing Trillian protos in a separate repo #2082

Open
DazWilkin opened this issue Apr 7, 2020 · 0 comments
Open

LOW: Consider publishing Trillian protos in a separate repo #2082

DazWilkin opened this issue Apr 7, 2020 · 0 comments
Labels
enhancement semver This PR/Issue likely affects semantic version. e.g. breaking API change
Projects

Comments

@DazWilkin
Copy link
Contributor

Trillian's protos are embedded within this repo which includes the Golang implementation.

I'm playing around with Rust and have prototyped (!) a Rust SDK for Trillian using the protos. I have a potential solution in mind using Rust.

https://github.com/DazWilkin/rust-trillian

The SDK generates rust sources from the protos but, in order to get the (latest) protos, it must clone the entire Trillian repo (~22MB).

Because the protos are bundled with the Golang implementation, it's not easy (!?) to check for changes to the protos.

I appreciate that there isn't a continuous stream of builds being generated from these protos but, have you considered separating the protos from the Golang implementation to version these separately?

Is there a better way to solve this problem? What do you do e.g. for the Python SDK? Just copy the protos?

/the bad apple

@paulmattei paulmattei added this to Needs triage in Trillian Apr 9, 2020
@AlCutter AlCutter added the semver This PR/Issue likely affects semantic version. e.g. breaking API change label May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement semver This PR/Issue likely affects semantic version. e.g. breaking API change
Projects
Trillian
  
Needs triage
Development

No branches or pull requests

3 participants