haxelib install should not install dependencies if they exist as a "dev" or "git" library already

[jgranick]

When you run haxelib install, dependencies are installed, even if they already exist.

For example, if you have OpenFL and Lime set up as haxelib dev directories, installing HaxeFlixel will force the download of both libraries before finishing the install.

[ncannasse]

Oh, that's because we assume that "dev" is outdated. That should not be the case for dependencies indeed, unless the version number is explicitly required in the dependency

[nadako]

This is now fixed thanks to @ibilon, however note that we want to lose dev-mode for git/hg installs (see #263 and #238), which means that it'll probably "consider vcs checkouts it as outdated" again at some point. This is probably correct however, because we also want to implement multiple vcs checkouts support (see #238).

[grosmar]

which means that it'll probably "consider vcs checkouts it as outdated" again at some point

Actually there is an implementation in haxelib to update the repository (haxelib update), and according to the changes that i make won't clone the repository again when you will call haxelib install ...
So this way all your local changes will remain there.

I hope i've understood correctly the problem...