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

Add cardano-blueprint submodule and move handshake cddl to it #5056

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ch1bo
Copy link

@ch1bo ch1bo commented Jan 29, 2025

Description

This demonstrates how we could move the CDDL to a common repository and test against it from multiple implementations of the ouroboros protocols.

Git submodules are obviously only one way of managing this dependency.

Checklist

Quality

  • Commit sequence makes sense and have useful messages, see ref.
  • New tests are added and existing tests are updated.
  • Self-reviewed the PR.

Maintenance

  • Linked an issue or added the PR to the current sprint of ouroboros-network project.
  • Added labels.
  • Updated changelog files.
  • The documentation has been properly updated, see ref.

@ch1bo ch1bo force-pushed the cardano-blueprint-handshake-example branch from 9e8b6ac to a5f7956 Compare January 29, 2025 12:41
This demonstrates how we could move the CDDL to a common repository and
tested against from multiple implementations of the ouroboros protocols.

Git submodules are obviously only one way of managing this dependency.
@ch1bo ch1bo force-pushed the cardano-blueprint-handshake-example branch from a5f7956 to 7f78055 Compare January 30, 2025 10:12
@ch1bo
Copy link
Author

ch1bo commented Jan 30, 2025

@coot I'd love to use this PR as a basis for discussion on how we could move the CDDLs into a place where they are more easily consumed by other implementations.

@coot
Copy link
Contributor

coot commented Feb 1, 2025

@ch1bo, such an approach will work, but first, this should be discussed in a wider forum, e.g. with consensus & ledger teams. We should not corner them with a decision like that.

I haven't used git-submodules extensively, but enough to know it can be painful. Are there other possible approaches which avoid git-submodules?

Can one use tags instead of git-hashes? It would be much nicer to say node-to-node-v14, isn't it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants