-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Update Ubuntu build instructions #1651
Comments
I prefer to link to the new build instructions in the root directory of the project, in the conventionally named file I would like to collaborate on fixing up the build instructions in the repository:
I think it's totally fine to add a Japanese translation to the source repo. Perhaps we can add a note at the top to warn readers to check the difference between the last time the English and Japanese versions were changed. |
I recommend deleting what's on xrpl.org (as it's out of date / obsolete anyway) and pointing people to instructions in rippled repo. |
Just recently the steps needed to build rippled on Ubuntu changed (starting with dev versions of 1.10.0) to use Conan to manage packages. This means changes to the build instructions.
Upstream PR: XRPLF/rippled#4367
Related: #1650, #1648.
Add any new dependencies and modify the steps as necessary to build on supported (current) versions of Ubuntu.
Aside: future of build instructions
It has been previously discussed, and might still be a good idea, to remove the separate build instructions on the xrpl website and only link the instructions in the source repo, since the method of building is specific to the release version. The repo also has build instructions for more platforms. We would like to first make sure the build instructions in the repo are clear and easy enough to follow, though, which might mean making PRs against the
rippled
repo to update them there.There's also the consideration that the website has Japanese-translated build instructions, which aren't kept perfectly up-to-date with the English but are probably better than nothing for native Japanese speakers; so we might want to port those to the upstream repo as well, but the team may not want to be responsible for those since they it would probably require someone fluent in Japanese to keep things updated as well.
The text was updated successfully, but these errors were encountered: