Lix/Lobby

Philippe

@elsassph

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

hmm LIBCACHE? https://github.com/lix-pm/haxeshim/blob/master/src/haxeshim/Scope.hx#L135

ah HAXE_ROOT should do it right? https://github.com/lix-pm/haxeshim/blob/master/src/haxeshim/Scope.hx#L539

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.

Kevin Leung

@kevinresol

lix install haxelib:lib#ver works already

lix install git:<url>#<hash/tag/branch> too

Philippe

@elsassph

Yes but I'd like to avoid putting the whole git URL just to switch branch/tag.

Juraj Kirchheim

@back2dos

tags can be modified, commit hashes can't

Philippe

@elsassph

Er well that would be silly but still, the point is could there be a shorthand to just change/update the repo to a branch/tag without writing the full qualified git URL.

Either using CLI or like npm where I can change the #branch in package.json and run npm install.

We use git repos heavily.

Juraj Kirchheim

@back2dos

yeah, my point hashes guarantee a specific state and tag names (which are really just branch names) don't, which is why lix uses those ... as does package-lock.json, by the way

Juraj Kirchheim

@back2dos

as for the rest, if editing a file and running a command is fine for you, you can just have a shell script with a bunch of lix install git:...#branch that you can edit and run ^^

Philippe

@elsassph

That kind of defeats using lix at all...

Juraj Kirchheim

@back2dos

if you say so

Where communities thrive

People

Repo info

Activity