Inconsistency with `bundle update`

chrismo / bundler-cases

Integration tests for Bundler

MIT License

0 stars 2 forks source link

Inconsistency with `bundle update` #6

Closed marcandre closed 8 years ago

marcandre commented 8 years ago

Here's a test case aiming to illustrate the inconsistency with bundle update foo with different --major/minor/patch. The only available gem versions are patches releases, so all three options should all behave the same but they don't for the minor and patch options.

I feel this inconsistency has to be bug. For sure, it makes it impossible to understand what is supposed to be going on.

chrismo commented 8 years ago

ah! very interesting. --major in this case defaults to not using any of the new code mechanisms in order to retain backward compatibility ... the idea being --major in 1.x would not change anything, so that in 2.x Bundler (2.0 only in dev right now) the default behavior could be switched to --patch.

Obviously something in the new code is affecting things it shouldn't in order to be consistent. Nice test case, thx!

chrismo commented 8 years ago

(we should probably file this bug with Bundler itself).

marcandre commented 8 years ago

Right, sorry. Moved