# haxe-ui
- b
bright-gpu-74537
09/16/2019, 9:54 PMyeah? - b
bright-gpu-74537
09/16/2019, 9:54 PMis that in agreement with me? - b
bright-gpu-74537
09/16/2019, 9:54 PMim not proposing a new standard - b
bright-gpu-74537
09/16/2019, 9:55 PMhaxelib is a "new" standard - b
bitter-family-72722
09/16/2019, 9:58 PMwhat's new about haxelib? - b
bright-gpu-74537
09/16/2019, 9:59 PMthat it doesnt work? That its git integration is bad (related to Std) - b
bright-yak-48460
09/16/2019, 9:59 PMSorry to jump in like this, but I'm confused... Can a haxelib like old haxeui not be gracefully retired? Would it be possible to replace the old haxeui with something that running haxeui install or update ran something to output to the console a message about retirement and how to install the newness? - b
bitter-family-72722
09/16/2019, 10:00 PMyeah, that's what we were talking about - b
bitter-family-72722
09/16/2019, 10:00 PMit could be updated to output a warning - b
bitter-family-72722
09/16/2019, 10:01 PMon compilation at least, not during installation.. - b
bitter-family-72722
09/16/2019, 10:01 PM(the latter seems preferable) - b
bright-gpu-74537
09/16/2019, 10:02 PMsure i could add a#warning("nope") - b
bright-yak-48460
09/16/2019, 10:02 PMI'm suggesting replacing the old haxeui with code that outputs as an act of running "haxelib install haxeui" with a message about retirement and instructions. As opposed to it installing and not seeing a message until u try doing something with old haxeui. Is there no way? - b
bitter-family-72722
09/16/2019, 10:03 PMno, I don't think Haxelib has any hooks that would allow you to execute code during / after installation - b
bright-gpu-74537
09/16/2019, 10:03 PMyou mean a deprecation on install? - b
bright-yak-48460
09/16/2019, 10:04 PMIf I follow you, yes - b
bright-gpu-74537
09/16/2019, 10:04 PMas far i understand, no, you cant go "dont use this one" - b
bright-gpu-74537
09/16/2019, 10:04 PMand, to be fair, for good reasons - b
bitter-family-72722
09/16/2019, 10:05 PMI mean, a deprecation warning on installation wouldn't do any harm I think - b
bitter-family-72722
09/16/2019, 10:05 PMpretty common in the NPM ecosystem I think? - b
bright-gpu-74537
09/16/2019, 10:06 PMit would be nice... but who is going to pay any real attention to that - b
bright-gpu-74537
09/16/2019, 10:07 PMmaybe if the repro is archive sometype of warning? - b
bright-yak-48460
09/16/2019, 10:07 PMI suppose if u could run code during/after install, openfl guys wouldn't require running "haxelib run openfl setup" after a fresh install. Just thought maybe "haxelib install whatever" might have the possibility of a return msg. - b
bright-gpu-74537
09/16/2019, 10:08 PMbut good luck changing anything in haxelib - b
bitter-family-72722
09/16/2019, 10:08 PMI mean, could be worse.. at least it's Haxe code 😄 - b
bright-gpu-74537
09/16/2019, 10:09 PMsure, its not about the lang - b
bright-gpu-74537
09/16/2019, 10:09 PMif i made a commit to haxelib, not, today, it going nowhere - b
bitter-family-72722
09/16/2019, 10:10 PM? - b
bright-gpu-74537
09/16/2019, 10:11 PMso PRs to haxelib are a thing? - b
bright-yak-48460
09/16/2019, 10:12 PM"haxelib install someWrongString" gives a msg, right? So there's a success/fail thing. Why can't a success return a custom msg, if it exists, from the json or xml or whatever is submitted for a haxelib?