diff options
| author | The Bundler Bot <bot@bundler.io> | 2018-03-27 19:47:41 +0000 |
|---|---|---|
| committer | The Bundler Bot <bot@bundler.io> | 2018-03-27 19:47:41 +0000 |
| commit | 77dbd12d0759ca635e3cb5cb0e90840cdac7f0d0 (patch) | |
| tree | 9ce0170dada9d2371a52b04b38fb5d063c51953f /man | |
| parent | 0fc3fc1c32bc633334df42aca3f7976c6444c24e (diff) | |
| parent | a936ef3761c1971055cc438180b43af4315f08f1 (diff) | |
| download | bundler-77dbd12d0759ca635e3cb5cb0e90840cdac7f0d0.tar.gz | |
Auto merge of #6305 - wagenet:fix-git-pristine, r=indirect
Correctly re-install extensions when running `pristine` for a git source
### What was the end-user problem that led to this PR?
I have a gem with a native extension that is installed via git. I had to recompile it due to some needed build arguments.
### The problem was...
Running `bundle pristine` would not recompile it as expected.
### My diagnosis was...
After digging into the source, I discovered that the built extension lived in a different location than the cloned git repo. `bundle pristine` was only removing the git repo so the built extension was not getting rebuilt.
### My fix...
Update `bundle pristine` to also remove the built extension. For 2.0, this also required removing the built extension cache. Without doing that, the built extension directory would just be recreated from the cache.
### I chose this fix because...
As far as I know, it's the only solution.
Resolves #6294
Diffstat (limited to 'man')
0 files changed, 0 insertions, 0 deletions