Where communities thrive


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

    back2dos on master

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

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

    kevinresol on master

    Guess cp for the kha ecosystem (compare)

  • Oct 29 13:01

    kevinresol on master

    Update haxeshim Release 15.10.1 (compare)

  • Oct 29 13:01

    kevinresol on v15.10.1

    (compare)

  • Oct 29 12:59

    kevinresol on master

    Fix shebang (compare)

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

    kevinresol on master

    Closes #151 (compare)

  • Oct 29 12:52

    kevinresol on master

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

  • Oct 29 12:07

    kevinresol on v15.10.0

    (compare)

  • Oct 29 12:07

    kevinresol on master

    Release 15.10.0 (compare)

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.
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)
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?