-
Notifications
You must be signed in to change notification settings - Fork 80
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
'latest' build definitions #145
Comments
👌 this would be great for automating dev machine setup. I have to imagine 90% of installs are "whatever latest LTS is" |
Yeah, came here to effectively post the same thing — to be clear, it's a terrible idea to have it installed as “latest”, so this definitely needs the same thing that #159 brought up, by the way. Previously, on tl;dr seems to me nodenv / node-build is sorely missing install aliases — arguments you pass to |
Just following-up on this — reinstalled Nodenv today, spent five minutes trying to figure out why Is this just blocked by the overall lack of implementation for aliasing? Or is this a wontfix / unwanted behaviour? |
It's definitely not wontfix. I wouldn't say it's blocked, but the implementation is not straightforward. I've attempted a handful of alternate approaches that each have some annoyances and downsides. I should have some time soon to wrap it up, though. |
bump :) |
|
Should we have some 'latest' build definitions that are always pointing to latest releases? The nodejs distributions list includes:
We could just have some build definitions that point to those locations, though that would mean the local install name of those nodes would be
node-latest
ornode-latest-v5.x
; since the version name would be taken from the build definition and not "updated" after installation to reflect the actual version number.Alternatively, we could try some kind of after-install hook to rename the version once it's installed.
Is this a good or bad idea? It seems the rbenv team have avoided this for a long time. Presumably they have reason?
nvm
has similar aliases likenode
which points to latest release and5.0
which is latest 5.x release.The text was updated successfully, but these errors were encountered: