aboutsummaryrefslogtreecommitdiffstats
path: root/lib/bundler/ruby_dsl.rb
diff options
context:
space:
mode:
authorHomu <homu@barosl.com>2016-08-04 14:53:12 +0900
committerHomu <homu@barosl.com>2016-08-04 14:53:12 +0900
commite511f9f4bcbcfc23e363a67c83b66386543cc02c (patch)
treef7076f3be3afd4e92fa2fd3ef8a0f092513620f4 /lib/bundler/ruby_dsl.rb
parentdda6432b71043b8065080f2fb83358614c4d04e8 (diff)
parent6117de98bb696a68cc15963b40d9157925e175a2 (diff)
downloadbundler-e511f9f4bcbcfc23e363a67c83b66386543cc02c.tar.gz
Auto merge of #4765 - mistydemeo:linkage, r=indirect
WIP: add command to check dynamic library linkage This new command, linkage, checks for broken dynamic library links in C extensions. I'd heard there was some interest in adding this functionality, so I thought I'd submit a preliminary PR for discussion. In my experience, broken dylib linkage is a common issue with C extensions, so I think having a good way to diagnose it would be valuable. This command scans all of the specifications in the bundle for .bundle files in C extensions. If any of the dynamic libraries linked against no longer exist, bundler will report a message to the console and exit non-0. TODOs: * Add support for non-Darwin OSs * Improve tests A few questions: * Is there a good way to mock functionality in the tests? Doing it in the standard rspec way isn't working since `bundle :command` runs in a subprocess. I'd like to be able to stub out stuff that actually checks dylibs and the like. * Is making this a new command the right approach? I assumed this wouldn't be ideal to include in, say, `check` because it would slow it down.
Diffstat (limited to 'lib/bundler/ruby_dsl.rb')
0 files changed, 0 insertions, 0 deletions