Vendoring content of cardano-crypto in cardano-addresses

Open
  • Is something wrong?
#102 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
build-system, cryptography

Research direction

Start by reviewing the cardano-crypto code and its dependency relationship with cardano-addresses, including the outdated packages mentioned in the issue. Define a vendoring approach that preserves the needed code while removing the external dependency; done means cardano-addresses can use the code without depending on cardano-crypto and its dragged-in packages.

Written by the indexing model from the issue text.

Description

We all agree cardano-crypto is old and mostly unmaintained, except for some time @erikd is kindly dedicating to it. Keeping it around as a dependency now that cardano-addresses moved to hackage is annoying, esp. as it also drags with it dependencies on other unmaintained or outdated packages (eg. basement).

We still need the code though and would like to "vendor" it in cardano-addresses codebase. How would that work?

Dominant language
C
Stars
68
Forks
45
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/cardano-crypto

All issues in IntersectMBO/cardano-crypto

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.