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

polkadot-omni-node: re-namings #5566

Open
3 tasks done
kianenigma opened this issue Sep 3, 2024 · 1 comment · May be fixed by #6057
Open
3 tasks done

polkadot-omni-node: re-namings #5566

kianenigma opened this issue Sep 3, 2024 · 1 comment · May be fixed by #6057
Assignees

Comments

@kianenigma
Copy link
Contributor

kianenigma commented Sep 3, 2024

  • Rename existing polkadot-parachain to polkadot-omni-node, and the existing polkadot-parachain-lib to polkadot-omni-node-lib.
  • Remove any hardcoded chain-spec from polkadot-omni-node
  • Then, Create a new polkadot-parachain that is now an instantiation of polkadot-omni-node-lib with system chain specs hardcoded.

A continuation of: #3944

It would be good to do this sooner rather than later to prevent breaking the names any longer.

github-merge-queue bot pushed a commit that referenced this issue Oct 8, 2024
- moved the omni-node lib from
  `cumulus/polkadot-parachain/polkadot-parachain-lib` to
  `cumulus/polkadot-omni-node/lib`
- renamed `polkadot-parachain-lib` to `polkadot-omni-node-lib`
- added `polkadot-omni-node` binary

Related to #5566
@serban300
Copy link
Contributor

Performed the renamings as part of #5915

Left to do:

  • Publish the polkadot-omni-node binary

@serban300 serban300 linked a pull request Oct 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Milestone 0
Development

Successfully merging a pull request may close this issue.

2 participants