You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running Fedora Server on a Raspberry Pi (because awesome), and was hoping to install nodejs via asdf. Unfortunately as far as I can tell asdf only offers the standard Intel packages. Node.js does offer ARM binaries, so the only trick is to convince asdf to pull the right package.
It seems like it would be important for this feature to not interfere with the 99% of other use cases, so maybe an opt-in feature? I'm picturing something like a line in a settings file that tells asdf to prefer ARM packages when available. Actually, it should be possible to detect the architecture of the current environment, and get the appropriate package from there.
The text was updated successfully, but these errors were encountered:
@Jwashton Yes we want to support Raspberry Pi ~! Thanks for the PR with Fedora instructions. Please tell us or PR if any changes are required to make things better on the Pi.
@Jwashton I'm closing this issue since it seems like this is something individual plugins should be responsible for. I'm not sure there is anything else asdf itself can do to make this easier. We definitely want asdf to work on other architectures though, so if there is something else that needs addressed please reopen this issue.
I'm running Fedora Server on a Raspberry Pi (because awesome), and was hoping to install nodejs via asdf. Unfortunately as far as I can tell asdf only offers the standard Intel packages. Node.js does offer ARM binaries, so the only trick is to convince asdf to pull the right package.
It seems like it would be important for this feature to not interfere with the 99% of other use cases, so maybe an opt-in feature? I'm picturing something like a line in a settings file that tells asdf to prefer ARM packages when available.Actually, it should be possible to detect the architecture of the current environment, and get the appropriate package from there.The text was updated successfully, but these errors were encountered: