All packages may need to be disabled if one of their dependencies is updated

[deathaxe]

I recently run into an issue when Package Control tried to update the lxml dependency. It was locked by either Exalt or xpath and therefore could not be updated at all. PC ended up in suggesting a reboot.

By simply disabling Exalt and xpath, the dependency was upgraded correctly after all.

[evandrocoan]

It could be a problem if a dependency is used by too many packages, because for example, I have about 170 packages installed and if I put all of the at once as ignored_packages Sublime Text does not take it well and keep hanging for a long time. Perhaps this deserve an issue on the Core issue tracker (Done: sublimehq/sublime_text#2155 Hanging when adding several packages to the ignored_packages setting)

But if these packages are locking the dependency, then Package Control is putting the dependency as a ignored_package and when Sublime Text start, these packages will fail to start because their dependency is not available. But now Package Control can update the dependency as no one is using.

Indeed, disabling the packages which require the dependency before disabling the dependency for upgrade would allow, or at least should help updating the dependency without requiring 2 restarts of Sublime Text. But perhaps the packages can lock the dependency files in such way that even unloading the package, would not release the dependency files without restarting Sublime Text as currently is required/performed.