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
vagrant: Clean up Gemfile #47310
vagrant: Clean up Gemfile #47310
Conversation
@Mic92 please let me know if there was a specific reason you made that change that I'm missing - I'm not super familiar with Ruby, but AFAIK it's not needed and is yet another place that would have to be kept updated during version bumps. |
Success on aarch64-linux (full log) Attempted: vagrant Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: vagrant Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: vagrant Partial log (click to expand)
|
I think they did not have an update to date version of vagrant at the time on rubygems. |
@Mic92 Thanks for the review. |
@aneeshusa but how does the Gemfile work then, if it does not get the information from rubygems? I think we should revert this in that case. |
Fetching from Github seems then the only viable option to me. We definitely don't want the omnibus version. |
It seems to me like we should just be running bundix on the Vagrant source repo, then commiting the gemset.nix? I don't think there's any reason for having the Gemfile and Gemfile.lock in nixpkgs, is there? |
|
Could we not give |
Should be possible: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/ruby-modules/bundled-common/default.nix#L82 |
Motivation for this change
@alyssais pointed out that @Mic92 changed this from the original.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)