c_xong {l Wrote}:How would you do it if instead of Haxe, it was GCC? You would need to download the source and make. Also if you don't like package managers you don't have to use haxelib, just download the package directly from
https://lib.haxe.org/.
I like package managers. I don't like having multiple package managers. I like visibility in my package manager. If I ask to install A, it tells me it will install B and C. If I try to run a command, I don't expect it to notice that it is not installed and install it without asking me. Part of the problem with haxelib is I don't know what it does. Does it just download files and put them somewhere or does it run scripts? Fedora has strong rules about package quality. Does haxe have strong standards? By having packages created by Fedora community, you can expect everything to just work. If I install haxe from Fedora package and then try to install a haxelib, I can find the latest version doesn't work with Fedora's version of haxe. (Looks like the developers behind haxe maintain the packages for Fedora so that probably isn't a big deal.)
The lack of information is disturbing to me. To setup openfl, I'm instructed to run 'haxelib install openfl' and 'haxelib run openfl setup'. I get what the first command does in general. What is the second command doing? Want to create your own project using openfl run 'openfl create project HelloWorld'. Want to use haxefixel, use 'flixel tpl -n "HelloWorld"'. What are these commands doing? Why is each library creating a new command to do it?
EDIT: I decided to download the hxcpp library to see what it includes. It don't see anything suggesting it runs a script but it does include some binary libraries. So if you install hxcpp, you have another install of zlib on the system.