Explicit 'chef' dependency for the plugin

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: ec2-0.5.12
  • Component/s: knife-ec2
  • Labels:
    None

Description

The knife-ec2 plugin does not explicity depend on 'chef'. The historical reason is unknown, adding it back.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Matt Ray added a comment -

merged to master
https://github.com/opscode/knife-ec2/commit/a8b261188d115d2e681c7d13a60f9834e8f6e657

Show
Matt Ray added a comment - merged to master https://github.com/opscode/knife-ec2/commit/a8b261188d115d2e681c7d13a60f9834e8f6e657
Hide
Permalink
Bryan McLellan [Opscode] added a comment -

I think our concern was that if you had a version of chef installed that was not the latest version and you installed the latest version of knife-ec2 using RubyGems, it would pull in the latest version if chef as well. I verified this doesn't happen with RubyGems 1.3.7 and 1.8.2 installing from a Gem, but I did not test it installing from a Gem server.

Show
Bryan McLellan [Opscode] added a comment - I think our concern was that if you had a version of chef installed that was not the latest version and you installed the latest version of knife-ec2 using RubyGems, it would pull in the latest version if chef as well. I verified this doesn't happen with RubyGems 1.3.7 and 1.8.2 installing from a Gem, but I did not test it installing from a Gem server.

People

  • Assignee:
    Matt Ray
    Reporter:
    Bryan McLellan [Opscode]
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: