# haxe-ui
- b
bitter-family-72722
09/16/2019, 10:13 PMit could, if it was implemented - b
bitter-family-72722
09/16/2019, 10:13 PM@bright-gpu-74537 the recent commit history seems to be mostly merged PRs - b
bright-gpu-74537
09/16/2019, 10:13 PMso i could "clean it up"? - b
bright-gpu-74537
09/16/2019, 10:14 PMdoubtful at best - b
bright-yak-48460
09/16/2019, 10:14 PMI like where this is going and will STFU now. :) - b
bright-gpu-74537
09/16/2019, 10:15 PMDave - b
bright-gpu-74537
09/16/2019, 10:15 PMyou are also part - b
bright-gpu-74537
09/16/2019, 10:15 PMyou use haxe? haxelib? - b
bright-gpu-74537
09/16/2019, 10:16 PM@bitter-family-72722 if i rewrote haxelib (client) it would never happen - b
bright-yak-48460
09/16/2019, 10:16 PMHaha. I do. Just don't wanna impede progress in an area I know little about. Just doesn't seem like a hard fix... if possibly adopted. - b
bright-gpu-74537
09/16/2019, 10:17 PMand i did btw - b
bright-gpu-74537
09/16/2019, 10:17 PMhaxelib is "ok" - b
bright-gpu-74537
09/16/2019, 10:17 PMit does its job - b
bright-gpu-74537
09/16/2019, 10:20 PMwill a PR from me ever be accpted? (wrt to haxelib) - b
bright-yak-48460
09/16/2019, 10:21 PMIf we made such an update to allow a msg back after install success for the haxeui case (or better, failed on purpose), seems like it could help for many old libs that may be in similar straights. As Ian says, would that or any change make it in? Perhaps some noise on Haxe roundup would help? - b
bitter-family-72722
09/16/2019, 10:22 PM@bright-gpu-74537 it's not up to me, but if it's a sensible change, why not? other PRs have been merged too after all - b
bright-gpu-74537
09/16/2019, 10:22 PMyou miss my point Jens - b
bitter-family-72722
09/16/2019, 10:22 PMbut something like a complete rewrite might be a bit problematic in a PR 😄 rather hard to review.. - b
bright-gpu-74537
09/16/2019, 10:22 PMexactly - b
bright-gpu-74537
09/16/2019, 10:23 PMbut you dont think it needs a rewrite, correct? - b
bitter-family-72722
09/16/2019, 10:23 PMpersonally I think that effort would be better spent making lix the de-facto solution / eventually replace Haxelib - b
bright-yak-48460
09/16/2019, 10:23 PMIan, would what I'm suggesting be enough of a bandaid for this sort of thing? - b
bright-gpu-74537
09/16/2019, 10:24 PMi think G just said it - b
bright-gpu-74537
09/16/2019, 10:24 PMJuraj already fixed it - b
bitter-family-72722
09/16/2019, 10:24 PMhm, I don't think lix supports deprecation warnings either 😄 - b
bright-gpu-74537
09/16/2019, 10:25 PMsure - b
bright-gpu-74537
09/16/2019, 10:25 PMi want talking about depreciation warnings, ofc. - b
bright-yak-48460
09/16/2019, 10:26 PMHaven't used lix. I got the perhaps wrong impression it was more for the Linux guys at this stage, no? - b
bitter-family-72722
09/16/2019, 10:26 PMlinux? how so? - b
bright-gpu-74537
09/16/2019, 10:26 PMnope,its just compiling to a very specific set of dependancies