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
cocoapods-beta: init at 1.7.0.beta.3 #59252
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The commit message does not follow the guidelines. Sorry.
@matthiasbeyer Are you talking about the subject, or the body? I'm not aware of guidelines around the commit message body, and the subject should follow guidelines. I know our guidelines say to use the package name, not the attribute name, but I went back and checked the commit that introduced |
This pull request has been mentioned on Nix community. There might be relevant details there: https://discourse.nixos.org/t/rubygem-conflicts-with-ruby-packages/2636/5 |
Like `bundlerEnv`, the `gemdir` parameter to `bundlerApp` can be omitted if all 3 of `gemfile`, `lockfile`, and `gemset` are provided.
31eb1ac
to
35c8733
Compare
I've just updated this PR 2 with 2 changes:
|
The commit message is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bundlerApp
change looks good :)
@matthiasbeyer Oh oops, you're right. I'll fix it. |
35c8733
to
5aa0d26
Compare
Both issues (commit message and comma) have been fixed. |
rm -rf "$BUNDIX_CACHE" | ||
rm -rf .bundle | ||
bundler lock --update | ||
# For some reson `bundler lock` doesn't take a `--gemfile` flag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the BUNDLE_GEMFILE
environment variable work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just tested, looks like the answer is "no". I have to delete Gemfile-beta.lock first as apparently bundler lock --update
won't backdate a lockfile despite the documentation claiming that flag makes it ignore the current lockfile (🤦🏻♀️) but after doing that, passing env BUNDLE_GEMFILE=Gemfile-beta bundler lock --update --lockfile=Gemfile-beta.lock
produces a lockfile that's clearly coming from Gemfile
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grr, okay. If you open a Bundler bug and add it to the comment, I'm happy to merge this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh. I just tested again to make sure and it actually seems like it's working now. I don't know what I did wrong before, since I double-checked my work last time, but if it really does work, I'll update this script to use that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woo!
cocoapods-beta is an alternative attribute for the cocoapods package that provides the latest beta instead of the stable version. Also switch to `bundlerApp` so we stop polluting the profile with our gem dependencies and can get rid of the broken `sandbox-pod` executable.
5aa0d26
to
ae22f7d
Compare
@alyssais PR updated to use |
Thanks @lilyball |
Motivation for this change
cocoapods-beta is an alternative attribute for the cocoapods package that provides the latest beta instead of the stable version.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)