Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 19 2020 12:11
    Aidan63 closed #83
  • Nov 27 2020 17:32
    back2dos closed #154
  • Nov 27 2020 17:32
    back2dos commented #154
  • Nov 27 2020 17:31
    back2dos commented #154
  • Nov 27 2020 17:11
    pawel-miczka opened #154
  • Nov 22 2020 14:02
    kevinresol commented #68
  • Nov 21 2020 21:15
    nulld opened #68
  • Nov 03 2020 12:32

    back2dos on master

    Update README.md Merge pull request #153 from Ri… (compare)

  • Nov 03 2020 12:32
    back2dos closed #153
  • Nov 03 2020 12:32
    back2dos commented #153
  • Nov 03 2020 11:26
    RichardBray opened #153
  • Oct 31 2020 11:31
    flammehawk opened #152
  • Oct 29 2020 14:34

    kevinresol on master

    Guess cp for the kha ecosystem (compare)

  • Oct 29 2020 13:01

    kevinresol on master

    Update haxeshim Release 15.10.1 (compare)

  • Oct 29 2020 13:01

    kevinresol on v15.10.1

    (compare)

  • Oct 29 2020 12:59

    kevinresol on master

    Fix shebang (compare)

  • Oct 29 2020 12:54
    kevinresol closed #151
  • Oct 29 2020 12:54

    kevinresol on master

    Closes #151 (compare)

  • Oct 29 2020 12:52

    kevinresol on master

    Support main in haxelib.json (h… (compare)

  • Oct 29 2020 12:07

    kevinresol on v15.10.0

    (compare)

Thomas J. Webb
@thomasjwebb
bam it's downloading
Juraj Kirchheim
@back2dos
I hope it's the right version now :D
Thomas J. Webb
@thomasjwebb
Yeah that fixed it. Thanks! So this shouldn't be an issue on deploy servers and such since they don't have this already there crap baggage
Juraj Kirchheim
@back2dos
but I think I bumped it almost two years ago ^^
yeah, normally only early adopters should be facing this problem on their machines ... only the cool kids!
Thomas J. Webb
@thomasjwebb
Yeah I installed lix globally more recently than that on this machine, but it's possible I accidentally let it install an old haxe version even though I've been using 4 since it was in rc stage
Philippe
@elsassph
Oh hi, I'm trying to do haxelib run formatter ... with lix but fail miserably
Juraj Kirchheim
@back2dos
hmm, formatter 1.11.0 + lix 15.9.0 seem to work just fine for me
can you illustrate your misery any further? ^^
Philippe
@elsassph
I must not understand how to map haxelib run formatter ... to lix.
Closest to something which almost works is lix run-haxelib . formatter ... which fails with
Unknown command run-dir
Haxe Library Manager 3.3.0 ...
I have latest lix / latest haxe as far as I can tell
Juraj Kirchheim
@back2dos
hmm, seems like a precedence thing
lix formatter and lix run formatter should work for global lix
but so should haxelib run formatter
Juraj Kirchheim
@back2dos
here's a fully isolated setup: mkdir foo && cd foo && npm init -y && npm i lix && npx lix scope create && npx lix install haxelib:formatter && npx lix formatter
works for me even if I have no lix installed and whether or not I have haxe and haxelib installed globally through the normal installer .. can you try that please?
Philippe
@elsassph
Hmm ok so lix formatter works when run as a npm script, but not in the terminal.
VSCode's integrated terminal. And scoped lix. Not adding npx if that matters.
Well that matters visibly :D
Juraj Kirchheim
@back2dos
lix formatter should work if and only if you've install lix via npm i -g lix
Philippe
@elsassph
I'd have thought that a global lix running in a scoped location would figure things out...
Juraj Kirchheim
@back2dos
hmm, ordinarily it does, but as always, there's a dozen things that can go wrong
tbh, I don't even understand how you managed to get lix and nonshimmed haxelib in the same $PATH (as your output fromlix run-haxelib . formatter indicates) ... that takes a quite peculiar setup ... are you throwing npm-haxe in the mix or something? ^^
Philippe
@elsassph
Haha no it's a clean lix setup. But I may have an old static install of haxe.
Philippe
@elsassph
Got a very interesting issue in CI: I forgot lix download and when building I got
haxelib path: /root/haxe/versions/4.1.2/haxelib: error while loading shared libraries: libneko.so.2: cannot open shared object file: No such file or directory
Juraj Kirchheim
@back2dos
where's haxelib from in that case?
Philippe
@elsassph
I dont know, I just ran npx haxe build.hxml which contains -lib. It's a clean Node docker image and lix only downloaded Haxe.
Juraj Kirchheim
@back2dos
ok, I managed to repro that ;)
Kevin Leung
@kevinresol
how to use git: protocol to fetch a particular branch?
tried lix install --flat git:https://gitlab.com/<org>/<repo>.git\#<branch> but gave me Cannot resolve version <branch>
Kevin Leung
@kevinresol
my bad, i forgot to actually push the branch to remote
so it is now able to resolve the SHA but unable to download:
downloading git:https://gitlab.com/<org>/<repo>.git#<sha>
From https://gitlab.com/<org>/<repo>
 * branch              HEAD       -> FETCH_HEAD
fatal: reference is not a tree: <sha>
Juraj Kirchheim
@back2dos
oh, wow, cool ... can you give details on how to repro that? Andre from innogames asked me about this, but he had solved it by killing his library cache and a clean install worked
Juraj Kirchheim
@back2dos
can you check the repo in ~/haxe/haxe_libraries/.gitrepos or similar?
Kevin Leung
@kevinresol
I fixed it and made a release 15.9.1
it is about the git fetch command
Philippe
@elsassph
CI question: where does lix store its cache? Could it be optionally located in the npm cache area?
Philippe
@elsassph
Yay export HAXE_ROOT=~/.npm/_haxe
Kevin Leung
@kevinresol
ya, I am using HAXESHIM_ROOT though, but I think this is deprecated
Philippe
@elsassph
We have a few libs where haxelib.json is not at the root of the git repo - how should I manage that?
haxelib git has an option to specify a subfolder
Is there a shorthand to update a library to a specific version? Thinking about haxelib but also git tags.
Kevin Leung
@kevinresol
lib#ver
Juraj Kirchheim
@back2dos
please open an issue about the subfolder thing ;)
Philippe
@elsassph
I mean for the git lib tag, I have to specify the full git URL everytime I just want to point to another tag - that's... suboptimal
Juraj Kirchheim
@back2dos
where's a near-optimal solution we could steal? ^^
Philippe
@elsassph
Some set-version libname#1.2.3 maybe, which would intelligently work with haxelib and git tags? Alternatively wondering if the git tags handling could be smarter: the tag is translated into the commit hash, whike the tag shoukd be unique enough.