Force gem dependencies to rebuild if I run rake gems:build:force

See #2678 Recursively unpack gem dependencies *and their dependencies* for comments about passing the whole options hash.

@Graeme - can you take a look at the patch on #2773 Rollup: Fix issues with 2.3.2 gem loader? It incorporates David's suggestion by passing the entire options hash to dependencies' build.

I'm happy for this ticket to be closed alongside #2773 Rollup: Fix issues with 2.3.2 gem loader being resolved.

(from [41a94048e55e082f373e19d9fcee311860aaba9e]) Fix several issues with the 2.3.2 gem loader.

Incorporates the following:

• migrates back small change to gems:build:force from bfc1609a501fc3ed442685819de5bcdb5fbada1c to finish closing #2266 rake gems broken for vendored gems which are unbuilt extensions.

• unrolls to_proc calls in gems.rake, to match the change in master.

• fixes #2722 Force gem dependencies to rebuild if I run rake gems:build:force by passing the options hash to dependencies during build. (includes a test)

• fixes #2721 Vendor gem failing rake gems:build by loading the specification directly in from_directory_name. Adds an option to opt-out of specification loading when needed (in gems:refresh_specs, for instance). Includes tests.

• fixes #2679 rake gems:refresh_specs should refresh all frozen gems by refreshing specs for all frozen gems rather than just gems loaded from the environment.

• fixes #2678 Recursively unpack gem dependencies *and their dependencies* by passing the options hash to dependencies during unpack.

Signed-off-by: Michael Koziarski michael@koziarski.com
http://github.com/rails/rails/commit/41a94048e55e082f373e19d9fcee31...