Page MenuHomeSolus

Initial commit of ruby-bcrypt_pbkdf
ClosedPublic

Authored by der_eismann on Nov 23 2018, 11:56 AM.
Tags
None
Referenced Files
F11065233: D4434.diff
Fri, Aug 11, 4:24 PM
F11046906: D4434.diff
Thu, Aug 10, 2:26 PM
F11008726: D4434.diff
Wed, Aug 2, 5:40 AM
F10981033: D4434.id10990.diff
Sun, Jul 23, 5:44 AM
F10899471: D4434.diff
Jul 3 2023, 5:46 PM
F10868311: D4434.id10880.diff
Jun 17 2023, 11:02 PM
F10868285: D4434.id10993.diff
Jun 17 2023, 10:57 PM
F10864422: D4434.id10990.diff
Jun 17 2023, 7:55 AM
Subscribers

Details

Summary

Initial commit, needed for Vagrant 2.2.1

Test Plan

Runs with Vagrant 2.2.1

Diff Detail

Branch
master
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Is there any reason these are being built from the .gemspec's via git? I thought they were basically converted to a single file .gem, kinda like a tarball of the sources with metadata.

Is there any guideline how ruby gems should be handled? Here it downloads the gem and then installs it, downloading the tarball works as well.

No, hence asking questions since I don't know ruby (outside of creating the macros and splitting vagrant). To me it seems like the more official builds seem to be via rubygems, where git is the development. 95% of the time these might be the same. These will be what you get when you install the packages via ruby so unless there is a reason to do otherwise, it seems the most logical option.

This revision is now accepted and ready to land.Nov 28 2018, 9:39 AM
This revision was automatically updated to reflect the committed changes.