Lix/Lobby

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

I'm confused what you're asking for ... I asked about a package manager that does what you want and the only example you've produced is editing a file by hand and then running a command ... this is already possible

Philippe

@elsassph

I can't just change the version in lix's generated hxml - the version appears half a dozen of times and I need to also update the commit hash. Eh nevermind I guess, it's visibly not a concern for you so I'll try to spec it and maybe propose a PR.

Juraj Kirchheim

@back2dos

well, I just type in stuff and when that becomes a nuisance, I make a script

e.g. you can put this into ./scripts/Git.hx:

package ;

import Sys.*;

class Git {
  static function main() 
    switch args() {
      case [repo, version]:
        exit(command('lix', ['install', 'git:some.domain/$repo.git#$version']));
      default:
        println('name and version required');
        exit(1);
    }
}

Juraj Kirchheim

@back2dos

and then lix Git somelib someversion will get the what you want (if I understand what you want)

for further details, see https://github.com/lix-pm/lix.client#scripting

Philippe

@elsassph

Look, I've been trying to convey that I'd like a built-in CLI option and you continue responding with variations of "type it or write a script" :D

Juraj Kirchheim

@back2dos

well, perhaps you should state your problem, rather than halfheartedly describing a feature ^^

I fail to see how lix set-version libname#1.2.3 solves a problem that e.g. lix Git libname 1.2.3 doesn't

Kevin Leung

@kevinresol

well I guess the issue of such solution is that you will have to copy the same script to every project?

Juraj Kirchheim

@back2dos

hmm, you can also make a lib called set-version and then lix set-version will call into that ... and you can make a lib that basically just bundles such "extensions" as dependencies

Kevin Leung

@kevinresol

using libs as lix extension seems quite practical

and interesting

Philippe

@elsassph

But I have stated the problem! For a git dependencies, a CLI option to change the branch/version of the dep without having to specify the git URL. I'm not sure how to describe it differently...

Now using a lib itself for that might be a solution. I'll explore that.

Philippe

@elsassph

I'm trying to dev an option in lix client but it's a bit of a hassle to run it locally from source...

lix download / npx lix download sometimes work, sometimes no. Once I got the build to work I tried to use it in another project using npm link and now building doesn't work with a

sh: /Users/philippe.elsass/.nvm/versions/node/v10.15.3/bin/haxe: Permission denied

I'm still probably going to use the run-lib approach eventually but I wanted to try how contributing would look like.

Kevin Leung

@kevinresol

usually I just run the built lix.js directly

sth like /path/lix.client/bin/lix.js build.hxml

Philippe

@elsassph

Ok. I had to npm unlink then npm install lix -g again for things to work

I'll use the direct path instead I guess :D

Where communities thrive

People

Repo info

Activity