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

Remove reddsa from being a patch #205

Merged
merged 1 commit into from
Aug 25, 2023
Merged

Conversation

mariari
Copy link
Member

@mariari mariari commented Aug 23, 2023

Patches change how inner packages compile, this makes it so that if anyone uses the project as a library they too have to include the dependency as a patch, since this dep can work as a dependnecy and not a patch, it is moved into a dep

@@ -15,7 +15,7 @@ halo2_proofs = {version="0.3", features = ["dev-graph"]}
bitvec = "1"
subtle = { version = "2.3", default-features = false }
dyn-clone = "1.0"
reddsa = "0.5"
reddsa = {version = "0.5", git = "https://github.com/heliaxdev/reddsa.git", branch = "taiga"}
Copy link
Contributor

@bazzilic bazzilic Aug 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty sure if you do { git = ..., branch = ... }, then version = ... is ignored, as it just pulls the HEAD of the branch as the dependency.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we'd better remove the version =? It seems useless if we use the branch directly?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think so. Should be just
reddsa = { git = "https://github.com/heliaxdev/reddsa.git", branch = "taiga" }

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll open some more topics then, as some of the other dependencies have two specifications of what the revision should be

Patches change how inner packages compile, this makes it so that if
anyone uses the project as a library they too have to include the
dependency as a patch, since this dep can work as a dependnecy and not
a patch, it is moved into a dep
@mariari mariari merged commit 72b4833 into main Aug 25, 2023
7 checks passed
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

Successfully merging this pull request may close these issues.

3 participants