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

Try to use apt to install AvalancheGo #31

Closed
Nuttymoon opened this issue Mar 17, 2023 · 2 comments · Fixed by #38
Closed

Try to use apt to install AvalancheGo #31

Nuttymoon opened this issue Mar 17, 2023 · 2 comments · Fixed by #38
Assignees
Labels
enhancement New feature or request security

Comments

@Nuttymoon
Copy link
Contributor

Nuttymoon commented Mar 17, 2023

AvalancheGo now has an apt repository. See Binary Repository.

Note: this type of installation might not be compatible with our filesystem layout (that tries to respect the Linux FHS)

@Nuttymoon Nuttymoon added enhancement New feature or request security labels Mar 17, 2023
@Nuttymoon Nuttymoon changed the title Use apt to install AvalancheGo Try to use apt to install AvalancheGo Mar 17, 2023
@Nuttymoon Nuttymoon self-assigned this Mar 20, 2023
@Nuttymoon
Copy link
Contributor Author

When installing AvalancheGo using apt install avalanchego, the binary is placed under /usr/local/bin whereas we currently install it under /opt/avalanche/avalanchego/current. According to this discussion on the differences between /opt and /usr/local I would say that our installation is closer to the Linux FHS.

IMO we should keep our way of installing AvalancheGo. We can still find a way of verifying the binary integrity after downloading.

@leopaul36 what do you think?

@leopaul36
Copy link
Contributor

When installing AvalancheGo using apt install avalanchego, the binary is placed under /usr/local/bin whereas we currently install it under /opt/avalanche/avalanchego/current. According to this discussion on the differences between /opt and /usr/local I would say that our installation is closer to the Linux FHS.

IMO we should keep our way of installing AvalancheGo. We can still find a way of verifying the binary integrity after downloading.

@leopaul36 what do you think?

Agreed, let's keep the binaries in /opt. Plus I know they only support Ubuntu and macOS but if things change we're already compatible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request security
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants