-
Notifications
You must be signed in to change notification settings - Fork 5
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
Sort out clone machine edge cases #21
Comments
We have an additional mechanism to replace files by the unit-e version now. This covers some of the mentioned edge cases such as the README (and some more files). We do have to look at the remaining cases where things are renamed which shouldn't and cover them in the blacklists and such. I would suggest to do that once we have the final naming in place (dtr-org/unit-e#228) and we have adapted clonemachine to do the renaming accordingly (i.e. issue https://github.com/dtr-org/unit-e/issues/296). |
One more corner-case: In the help texts of the RPC commands there are various occurrences of "unite address". These should probably rather be "Unit-e address". |
One more edge case: |
Most of the edge cases have been resolved now. This is a summary of what is left to do:
|
The clone machine does trivial transformations of the bitcoin codebase. For example it renames
bitcoin
intounit-e
where it's safe to do so.Occasionally it renames some things (all in documentation, READMEs and such) which it shouldn't – for instance it renames names of python packages like
python-bitcoinlib
to things which actually should not exist.These should be changed back manually (it's not a terribly lot) and blacklisted in the clone machine. The clone machine already features mechanisms to black list certain items.
The text was updated successfully, but these errors were encountered: