Class | Gem::DependencyList |
In: |
lib/rubygems/dependency_list.rb
|
Parent: | Object |
Gem::DependencyList is used for installing and uninstalling gems in the correct order to avoid conflicts.
development | [RW] | Allows enabling/disabling use of development dependencies |
specs | [R] |
Creates a new DependencyList. If development is true, development dependencies will be included.
Return a list of the gem specifications in the dependency list, sorted in order so that no gemspec in the list depends on a gemspec earlier in the list.
This is useful when removing gems from a set of installed gems. By removing them in the returned order, you don‘t get into as many dependency issues.
If there are circular dependencies (yuck!), then gems will be returned in order until only the circular dependents and anything they reference are left. Then arbitrary gemspecs will be returned until the circular dependency is broken, after which gems will be returned in dependency order again.
Is is ok to remove a gemspec from the dependency list?
If removing the gemspec creates breaks a currently ok dependency, then it is NOT ok to remove the gemspec.
Remove everything in the DependencyList that matches but doesn‘t satisfy items in dependencies (a hash of gem names to arrays of dependencies).