Haxelib install useless prompts

[ncannasse]

I noticed when doing "haxelib install ufront" that I was getting messages such as:

Installing dependency hscript 2.0.4
You already have hscript version 2.0.4 installed
Set hscript to version 2.0.4 [y/n/a] ?

I guess that's because hscript (and some other dependencies) were required twice by different dependencies path.

Anyway, in that case we should skip the actual install, given it's already up to date.

[back2dos]

Maybe you got that because you have hscript on dev locally and haxelib wants to set it to the downloaded version instead?

On Tue, Jun 9, 2015 at 9:36 AM, Nicolas Cannasse [email protected] wrote:

I noticed when doing "haxelib install ufront" that I was getting messages such as:

Installing dependency hscript 2.0.4 You already have hscript version 2.0.4 installed Set hscript to version 2.0.4 [y/n/a] ?

I guess that's because hscript (and some other dependencies) were required twice by different dependencies path.

Anyway, in that case we should skip the actual install, given it's already up to date.

— Reply to this email directly or view it on GitHub https://github.com/HaxeFoundation/haxelib/issues/218.

[ibilon]

@back2dos even in that case, it'll set the version to the downloaded one but won't deactivate the dev version anyway, so asking a set is not the most useful here.

[back2dos]

Then that's a bug in version setting that if fixed makes this behavior sensible. That is, if that's why haxelib asked in the first place.

On Tue, Jun 9, 2015 at 10:09 AM, Valentin Lemière [email protected] wrote:

@back2dos https://github.com/back2dos even in that case, it'll set the version to the downloaded one but won't deactivate the dev version anyway, so asking a set is not the most useful here.

— Reply to this email directly or view it on GitHub https://github.com/HaxeFoundation/haxelib/issues/218#issuecomment-110269319 .

[ncannasse]

@back2dos I actually had hscript as dev version, but it also prompted it for other libraries I had never installed. Try with a fresh haxelib repo and install ufront to reproduce

[back2dos]

haxelib newrepo
haxelib install ufront

Here's the first prompt:

Installing dependency random
You already have random version 1.4.1 installed
Set random to version 1.4.1 [y/n/a] ?

With haxelib list yielding:

cleversort: [1.0.2] 1.0.3
compiletime: [2.5.1]
hscript: [2.0.4]
mcli: [0.1.4]
minject: [1.3.0] 1.6.1
PBKDF2: [1.0.0]
random: [1.4.0] 1.4.1 <----- asking is the correct behavior
thx.core: [0.17.7]
tink_core: [1.0.0-rc.11] 1.0.0-rc.7
tink_macro: 0.5.0 [0.6.4]
ufront-easyauth: [1.0.0-rc.10]
ufront-mvc: [1.0.0-rc.17]
ufront: [1.0.0-rc.13]

On it goes:

Installing dependency minject
You already have minject version 1.6.1 installed
Set minject to version 1.6.1 [y/n/a] ?

And:

Installing dependency thx.core
You already have thx.core version 0.23.0 installed
Set thx.core to version 0.23.0 [y/n/a] ?

And:

Installing dependency cleversort
You already have cleversort version 1.0.3 installed
Set cleversort to version 1.0.3 [y/n/a] ?

Where you can see in the above output, all those versions need to be set, because some dependencies explicitly installed lower versions.

The way I see it is that the haxelib server should have forbidden uploading conflicting dependency versions in the first place.