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

"#devel" isn't a version, flawed detection whether "current"... #331

Open
gwiede opened this issue Aug 25, 2023 · 0 comments
Open

"#devel" isn't a version, flawed detection whether "current"... #331

gwiede opened this issue Aug 25, 2023 · 0 comments

Comments

@gwiede
Copy link

gwiede commented Aug 25, 2023

Bug: Using "#devel" for nightlies version designation denies user ability to determine if local nightly is actually "current".

When a user selects "devel", the version designation for the nightly version is "#devel" (aside: note presence of '#' character that requires escaping in many common shells). Even if woefully outdated nightly is present, there is no means for user to distinguish that from a "current" nightly, because the version designation is ALWAYS shown as "#devel".

Alas, whatever inside choosenim is supposed to be tracking whether local "#devel" is "current" also appears broken: Even immediately after "choosenim update devel" successfully completes, "choosenim versions" indicates an update is available (and subsequent "choosenim update devel" cmds will indeed re-download and re-install the exact same nightly version they just installed).

To be clear, that "always new nightly available" issue merits its own bug, I'm only mentioning it here to highlight why using "#devel" instead of some actual versioned designation for nightlies creates problems for users as well.

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

1 participant