Last line:
./haxelib setup
results in the same error as any haxelib invokation attempt so far.
Haxe itself as always works.
I hope I don't sound rude but this is really bad, the built package from server was an extensionless tar in a .tar gzip in a .tar.gzip gzip, which is definitely an error and confuses tar.
Install script fails with cryptic errors, haxelib fails with cryptic errors, I had to download idiotic amount of dependencies(I think KDE weights less than OCaml + others) and then it still doesn't work. Site and internet has tons of outdated advice(such as 'if on 64 bit Mac spawn neko for 32 bit one', except it's said to not work anymore).
Why couldn't haxelib be written in something standard that comes with all unixes like python, sh, C or perl so that everyone could just read the code and debug it themselves?
I understand haxefoundation also makes neko but surely neko has less spread and adaptation than any of these four languages...
Definitely not the ease of setup that I imagined from
haxe.org page.
I was enthusiastic about haxe and now I'm vaguely interested and discouraged, I'll be keeping just haxe and deleting all dependencies I needed only for build or haxelib.
Let's put it that way: it took me less time building Lua on FreeBSD, Linux and Windows two or three times on each total than it did trying to setup haxelib(which still doesn't work).
And by setup I mean trying out every combination of built/downloaded haxelib and nekovm.
I'm giving up on trying to get haxelib to work, thank you for your help but it seems we both wasted our time.