ruby-modules: Import gemset if it's a path OR a string. #38959
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Commit comment:
This fixes the bug introduced by [@aneeshusa's] 8686b98 which broke bundlerEnv
exprs when gemdir was a string (thus making gemset a string by
gemset = gemdir + "/gemset.nix"
) which made it being treated as aset.
pkgs/development/ruby-modules/bundled-common/functions.nix
:pkgs/development/ruby-modules/bundled-common/default.nix
:I stumbled upon this because I set
gemdir
to the value of a filterSource expression, which is a string.Motivation for this change
Try building
pkgs/servers/monitoring/sensu/default.nix
on the latest master(e.g.92f0d31b949bcf018262
with this change:It ain't gonna build, but it did before.