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

'latest' build definitions #145

Open
jasonkarns opened this issue Apr 6, 2016 · 6 comments
Open

'latest' build definitions #145

jasonkarns opened this issue Apr 6, 2016 · 6 comments

Comments

@jasonkarns
Copy link
Member

jasonkarns commented Apr 6, 2016

Should we have some 'latest' build definitions that are always pointing to latest releases? The nodejs distributions list includes:

image

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 or node-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 like node which points to latest release and 5.0 which is latest 5.x release.

@searls
Copy link
Contributor

searls commented Dec 22, 2016

👌 this would be great for automating dev machine setup. I have to imagine 90% of installs are "whatever latest LTS is"

@ELLIOTTCABLE
Copy link

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 nvm, I could simply “nvm install latest” or “nvm install stable” or “nvm install nightly”, and it would do the obvious thing — and better yet, on a new-ish machine, I could nvm install v8 and nvm install v6 to install the latest of each of those releases.

tl;dr seems to me nodenv / node-build is sorely missing install aliases — arguments you pass to nodenv install that don't install precisely what you typed, but an intelligent interpretation thereof. (I wouldn't mind if this were locked behind a flag or something, for backwards compatibility — nodenv install -a/--approx v8, or something?)

@ELLIOTTCABLE
Copy link

Just following-up on this — reinstalled Nodenv today, spent five minutes trying to figure out why nodenv install v8 or nodenv install latest wasn't working, and ended up finding my own response to this Issue. 🤣

Is this just blocked by the overall lack of implementation for aliasing? Or is this a wontfix / unwanted behaviour? (=

@jasonkarns
Copy link
Member Author

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.

@shaharmor
Copy link

bump :)

@gianpaj
Copy link

gianpaj commented Mar 3, 2023

asdf uses node-build. It would be great if this would work

$ asdf install nodejs latest-lts
Trying to update node-build... ok
node-build: definition not found: latest-lts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants