diff options
| author | isaacs <i@izs.me> | 2011-02-15 02:04:17 +0300 |
|---|---|---|
| committer | isaacs <i@izs.me> | 2011-02-15 02:04:17 +0300 |
| commit | 5f0c267dfdf9ad3215a53fe2178c4bc30d2967b5 (patch) | |
| tree | d8e6657b67d5850093844100c3b42efc8585eba9 /lib/rebuild.js | |
| parent | 6a7838644218f76e9d53cc14a4b4997b23608d9e (diff) | |
Closes GH-542 On second thought, no.
There are several edge cases that one finds down that road.
Since the cached contents may have been discarded, this could
effectively become a 'reinstall' command. That'd be fine,
but I think for a sugar method like this, it takes things
just a bit too far.
Diffstat (limited to 'lib/rebuild.js')
| -rw-r--r-- | lib/rebuild.js | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/lib/rebuild.js b/lib/rebuild.js index 11c30150c..e78938a37 100644 --- a/lib/rebuild.js +++ b/lib/rebuild.js @@ -44,10 +44,6 @@ function rebuild (args, cb) { log.silly(folders,"rebuild folders") log.silly(actives, "rebuild actives") - //FIXME GH-542 - remove the folder and re-unpack into it. - // that probably means getting the tarball with - // cache.add() again. - // Look at how it's done in lib/install.js asyncMap(folders, function (arg, cb) { log.verbose(arg, "rebuild") var n = arg[0] |