haxelib Should 'haxelib local/haxelib install' disable the 'dev' version

I think that if a user has explicitly set a haxelib version, the dev version should be disabled.

Nov 24 '13 02:11 hughsando

I agree, the latest command should always trump previous ones.

Nov 27 '13 11:11 Simn

We have then to make difference between explicit install of a lib versus "upgrade"

Nov 27 '13 11:11 ncannasse

I kind of want to merge this with #265, but it seems that there was some consensus in this issue, while #265 proposes to either explicitly prompt dev unsetting or going even simplier way - just noting that user has the dev path set. What's the opinion nowadays?

Dec 22 '15 17:12 nadako

If think we can, in #265 there was two possibility but they are similar to what's discussed here: should an upgrade disable dev or just mention it, while install/local should do it (and probably mention it with the command to run to reactivate it like before).

Considering the purpose of dev I think an upgrade shouldn't remove it. I think that's what @ncannasse's comment means, otherwise there'd be no need to differentiate install and upgrade.

Mar 10 '16 15:03 ibilon