Project
Nu
Priority
Minor
Type
Feature
State
Submitted
Assignee
Unassigned
Subsystem
Client (nu)
Fix versions
No Fix versions
Affected versions
No Affected versions
Fixed in build
Next Build
  • Created by   Dru Sellers
    2 years ago (27 Jul 2010 12:56)
  • Updated by   Brendan
    2 years ago (28 Aug 2010 23:30)
 
NUPRJ-1 nu update - LOW PRIORITY
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
Would be nice to support update command through nu.
Please only target .net gems.
Comments (1)
 
History
 
Linked Issues (?)
 
Brendan
  Brendan
28 Aug 2010 23:30
2 years ago
Now that the individual package's gemspec is serialized into it's directory, Nu is in a good position to do this. It can find each of the projects that are at the tops of the dependency graphs and, with each of them:
1) ask gem to update to the latest version
2) remove all dependencies (owned only by that project)
3) `nu install` the project again

We should probably keep track, for each top-most project, if a specific version was requested with the –version flag. If so, it would be opted-out of the `nu update` command.