Monorepo ed/x/curve25519

[pinkforest]

As discussed this is the monorepo PR

• This would need to be merged - not squashed - in order to retain the combined history from x/ed/curve
• Renames for each crates in separate commit
• Merge commits for each combine
• CI re-organized for Monorepo structure
• This PR needs to be kept minimal and can follow-up with e.g. proper monorepo root README.md etc.
• This would help us keep the crates consistent and synchronized across and messing with git patching
• I was hoping commits could be prefixed-amended based on crate e.g. ed25519 could have ed: prefix and the PR links would be linked to old place - nonetheless this would be the tradeoff with history we would pay for easier consistency across the crates and usually the original commits has all the information from PR's

git combine Procedure (see near last commits)

git mv [curve25519-dalek-stuff] curve25519-dalek/
git commit -m 'Workspace curve25519 under curve25519-dalek'

git remote add ed https://github.com/dalek-cryptography/ed25519-dalek.git
git fetch ed
git merge ed/main --allow-unrelated-histories
git mv [ed25519-dalek-stuff] ed25519-dalek/
git commit -m 'Workspace ed25519 under ed25519-dalek'

git remote add x https://github.com/dalek-cryptography/x25519-dalek.git
git fetch x
git merge x/main --allow-unrelated-histories
git mv [x25519-dalek-stuff] x25519-dalek/
git commit -m 'Workspace x25519 under x25519-dalek'

[rozbb]

Thank you! Two things:

1. Is there anything we can do to merge the issues/Pars (current and past) from all the constituent repos? Or are we just stuck keeping or historical record in an archived repo?
2. If it's not too annoying, I'm gonna do the git merge steps myself. Just bc it's literally impossible to audit on my end. I'll cherry pick the follow-up commits you have here. Saw edited comment

[pinkforest]

1. We can transfer the issues, PR's would have to be re-created.
2. I have other changes too incl. CI and would have to audit in any case :)

This can be audited with ... rsync :)

$ rsync -rcnv a/* b/

-r will recurse into the directories
-c will compare based on file checksum
-n will run it as a "dry run" and make no changes, but just print out the files 
   that would be updated
-v will print the output to stdout verbosely

e.g. like this:

git clone https://github.com/dalek-cryptography/curve25519-dalek.git
git clone https://github.com/dalek-cryptography/ed25519-dalek.git
git clone https://github.com/dalek-cryptography/x5519-dalek.git
pull this pr to "monorepo"

rsync -rcnv monorepo/curve25519-dalek/* curve25519-dalek/
rsync -rcnv monorepo/ed25519-dalek/* ed25519-dalek/
rsync -rcnv monorepo/x25519-dalek/* x25519-dalek/

Above without 'dry run" you can also do "git status" to see if any files changed and how they changed "git diff" if any.

[rozbb]

Left some comments. Verified that the subdirectories match the current main branch of all the relevant repos (outside the necessary Cargo.toml changes). Used

diff -r ./curve25519-dalek ../curve25519-dalek

etc.

[rozbb]

Alright, made a pretty barebones README, but it should be OK for now imo. The dalek image doesn't load correctly anymore bc the URL is gonna change in this PR.

[pinkforest]

Ok - I had to re-organize our last commits since this PR needs a merge (not a squash) making it more difficult to change here (suggest doing more in follow-up PR's) and we have renames which need to be kept in separate commits in the middle. I gave you co-authored-by since I had to amend our last change commits on top.

[rozbb]

Gotta re-check the subdirs with diff again bc of the force push. But barring that good to go @tarcieri ?

Update: re-verfified. For concreteness, the current HEADs are:

• 2e3212b
• dalek-cryptography/ed25519-dalek@58a967f
• dalek-cryptography/x25519-dalek@8613b5a

[rozbb]

Build's broken now but I have no idea what's causing it 😕

[pinkforest]

Something broke in transient dependency somewhere for the MSRV build - this should be mergeable in any case as this doesn't cause it.

Found what caused it - raised #538 to track it