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

vendoring secretstream #1

Open
cryptix opened this issue Sep 17, 2016 · 4 comments
Open

vendoring secretstream #1

cryptix opened this issue Sep 17, 2016 · 4 comments

Comments

@cryptix
Copy link

cryptix commented Sep 17, 2016

I'd love to see a solution where changes to secstream flow upstream and don't only end up only in thirdparty/

what's the process at go-ipfs now? last time I worked on it it was still godeps but I think it's gx now?

cc @whyrusleeping @jbenet

@keks
Copy link
Owner

keks commented Sep 17, 2016

Thanks for filing that issue. I simply did what I found in the go-ipfs repository but am open for suggestions.
Also of course I would commit any changes to secstream upstream, it would only be a manual step.

@jbenet
Copy link

jbenet commented Sep 17, 2016

yeah probably gx-- @whyrusleeping and @Kubuxu will know best

@keks
Copy link
Owner

keks commented Sep 22, 2016

unvendored. I will provide a gx version of secretstream and add it to the package.json

@keks
Copy link
Owner

keks commented Sep 24, 2016

I added secretsteam to gx and have it as a dependency in package.json. Is everyone happy with this?

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

No branches or pull requests

3 participants