Updating module dependencies arch

One of the new features of Package Control 3.0 is support for dependencies.Dependencies are non-user-visible packages that contain binaries, shared libraries or Python modules.The solver uses the installed list to extract the installed features, but it doesn't add those solvers to the specs.

updating module dependencies arch-27updating module dependencies arch-17

[ COMPLETE ]|###################################################| 100% Rover:~ stan$ conda list -n dep_test pandas # packages in environment at /Users/stan/anaconda/envs/dep_test: # pandas 0.17.1 np110py34_0 Rover:~ stan$ conda list -n dep_test h5py # packages in environment at /Users/stan/anaconda/envs/dep_test: # h5py 2.5.0 np19py34_3 operation, only those in the dependency tree rooted in the packages explicitly listed on the command line.

(This issue probably duplicates other issues, but I haven't seen one that explains the problem generically.) , along with a list of the installed packages.

But all dependencies are---and all of their dependencies, too, all the way down. My point in including this use case was that when you had the comment above "The fix is, of course, to include the existing packages in the specs." I think I completely agreed, but it wasn't clear to me that you were also implementing the fix for the case. It's possible that the current fix isn't perfectly achieving this goal.

I am working on a larger fix to the solver that will do a better job of minimizing the disturbance to the environment when a single package is installed, but the priority is not to allow the environment to be broken. I think such a fix would change the --no-update-dependencies behavior from "Do not unnecessarily update dependencies in the package list I'm submitting to this command" to the more expected/intended "Do not unnecessarily update dependencies that are already installed in my working environment so this can be a minimal install". I'm working on a larger solver fix that should do so.

The dependencies in the default repository are tracked in the file repository/

Comments