FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

No more Windows fat binaries (or precompiled binaries at all) by tjschuck · Pull Request #174 · bcrypt-ruby/bcrypt-ruby · GitHub

Repository navigation

No more Windows fat binaries (or precompiled binaries at all) - #174

Merged
tjschuck merged 3 commits into
masterfrom
no_more_precompiled_binaries
Nov 9, 2018
Merged

tjschuck merged 3 commits into
masterfrom
no_more_precompiled_binaries

Conversation

Copy link
Copy Markdown
Collaborator

@tenderlove @larskanis Fixes #173.

We will now no longer provide compiled binaries at all, and particularly not Windows fat binaries. The AppVeyor config has been updated to now actually compile the lib and run the tests, not just install the gem like we were previously testing.

Copy link
Copy Markdown

Looks good! You're still putting effort into Ruby-1.8.7? Maybe you could drop old Ruby versions with bcrypt-4.0?

Copy link
Copy Markdown
Collaborator Author

@larskanis I'm fine with dropping 1.8 if we have to for some reason, but as long as it's possible to somewhat trivially support 1.8, I'd rather keep it alive strictly because this is a security-related library. If someone's dealing with some 1.8 legacy app, I don't want them to jump to SHA-1 just because the latest bcrypt-ruby doesn't install easily 😅 That said, emphasis on the "somewhat trivially" part of it.

For now, there hasn't been a huge cost to continue supporting 1.8.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL