Downgrades my gems

[vemv]

I'm a bit disappointed by the results from executing this gem (trying all possible settings)

So it takes rspec 3 and turns it into rspec 0.1. Umm...

Dunno if it's a parsing issue or an algorithm issue.

The algo should be dead-simple and it should absolutely not try to be smart:

• Take versions from Gemfile.lock
• Copy the numbers literally to the Gemfile (up to minor or patch level, depending on command-line options)

What do you think it happened?

Cheers - Victor

[joonty]

This definitely looks like a parsing issue - pessimize doesn't try and do anything clever with the numbers. I can sympathise with your disappointment!

It's been so long since you created this issue (sorry...), I can't expect you to still have the Gemfile or even care about pessimize, but I think you've given me enough information to reproduce the problem.

[vemv]

Hey there,

let me know if you have trouble reproducing the problem!

I might run pessimize through a few projects later if needed

[joonty]

@vemv I had trouble with the exact example, mainly because the available versions are obviously now different - I think it really depends on what was in your Gemfile.lock at the time.

I have a suspicion that it's related to #12, in that the versions in your Gemfile.lock may have been non-standard. I know rspec does that every so often. I'll keep trying a few things. Thanks for the reply!