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.

Sign up for GitHub

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

Jump to bottom

Add note re installing native gems with Bundler v2.2 #39

Merged
merged 1 commit into from
Oct 25, 2021
Merged

Add note re installing native gems with Bundler v2.2 #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/tutorials/installing_nokogiri.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,9 @@ Successfully installed nokogiri-1.11.0-x86_64-linux
1 gem installed
```

If you're using Bundler v2.2+, check your lockfile knows about your platform(s): see `man bundle-lock` for details.
flavorjones marked this conversation as resolved.
Show resolved Hide resolved


### Why would I not want to use a native gem?

I can imagine some folks might have trust issues; if this is you, please let us know in a comment at [RFC: Increase the level of trust in released gem files · Issue #2013 · sparklemotion/nokogiri](https://github.com/sparklemotion/nokogiri/issues/2013). What can we do to increase that trust? (I can imagine providing a chain of custody including public build logs with cryptographic hashes of artifacts, but I'd like to hear from real users.)
Expand Down