-
Notifications
You must be signed in to change notification settings - Fork 4
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
Cannot install Nim v0.19.2 #5
Comments
Yeah, it's a problem, but one I'm not likely to do much about due to time constraints and my complete lack of doing anything with nim in quite some time. @paradox460 demonstrated some willingness to take over supplying the plugin but no idea where he's at on that. I'll gladly give any pull requests a try, but... that's probably all I have to offer, at least currently. (I should probably find someone to take over the asdf-gradle plugin, also, but it hasn't given me any grief...) |
This isn't a very hard fix - just need to update |
To elaborate: thanks to @braunse for the pull request that does basically what @genotrance suggested and now the default build is working again, or at least the travis-ci build succeeds... |
@genotrance package maintenance uses softcoded bash replacements for the according to scripts. Raising the version in these build scripts currently leads to a fail. Simply hit that Github button to correct the links. I suggest always triggering a version release in csources, thanks a lot. |
I'm not sure what's being said here. The current plugin version builds v0.19.6 fine for me. (I goofed trying the first time, which is the only reason I reopened this. So closing it again unless someone reproduces and documents a problem.) (Also, it's basically a miracle I noticed anyone commenting. This and asdf-gradle really need new maintainers.) |
I agree with you. Getting new developers on board and potential new maintainers is a hard task. Currently, the default way is a bash script, which is considered the worst practice of all. Security concerns and the kind of implementation in the OS distract people immediately. Package maintainers often experience very sad descriptions in the build instructions and it often puzzles me, how many developers know very less about the common hurdles in packaging. To make a specific package a breeze to build and maintain increases the chances that this packages gets upstream, in the public repositories. Case solved. |
Another proof that nobody here in the team puts itself into the position of a potential packager: I personally see zero indication in the build instructions that the current x.0 csources is always the correct one for each according x.y version. |
The instructions on the website ask you to simply download the xz file that has everything prepackaged in one place. Downloading from github across repos is not required. The suggestion to use 0.x.0 was because the script was already using github so the change was minimal. What is the concern with the current implementation? |
As said, that does not sync with my distro-specific package manager. If I succeed to do so, I may loose the overview for all my packages and use effectively two different package manager solutions. Plus, since it probably adds Nim to /usr/bin or so, might it conflict sooner or later with the system libraries. And as said, the primary recommendation is blindly installing a bash script and that scares a significant number of people for obvious reasons. While I am well aware that you can read this file beforehand, it is still considered a shaddy practice. Thanks a lot :) |
I think there's a bunch of confusion here - this is the nim plugin for the asdf package manager. If you are a packager for some other package manager, this if the wrong forum. If not, the asdf package already works. If you have concerns with how asdf works, it is outside my expertise. If you are a packager for some other package manager, the recommendation is to use the xz file as your starting point since it comes with everything in it. Once you build it as described in the docs, you could then build a package out of it. It doesn't install per se. Everything goes into the bin subdir. Another suggestion is to see how other distros have included Nim. I know Ubuntu and Debian do. Hope that helps. |
That is all correct and does not affect what I have said. |
I tried but failed to install Nim v0.19.2:
Indeed, the csources repository does not contain a v0.19.2 tag or branch at the moment:
https://github.com/nim-lang/csources/tree/v0.19.2 -> Error 404
The latest csources tag is v0.19.0:
https://github.com/nim-lang/csources/tree/v0.19.2 -> Exists
The text was updated successfully, but these errors were encountered: