Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haxelib git without .git folder? #493

Open
CrazyFlasher opened this issue Feb 12, 2020 · 3 comments · May be fixed by #607
Open

haxelib git without .git folder? #493

CrazyFlasher opened this issue Feb 12, 2020 · 3 comments · May be fixed by #607

Comments

@CrazyFlasher
Copy link

CrazyFlasher commented Feb 12, 2020

Using Haxe 4.0.1

Is it possible to install haxelib with "haxelib git " command, but do not clone .git folder, that contains all history?

Git git cloning can be done that way in this case:

git clone --depth=1 <remote_repo_url>

If I run command like this haxelib git starling-extensions-hx https://github.com/CrazyFlasher/starling-extensions-hx.git --depth=1 haxelib clones, then deletes everything git folder because it's looking for branch --depth=1 :)

@RealyUniqueName
Copy link
Member

There's no such option in haxelib.
As a workaround you can clone a lib manually and then haxelib dev libname path/to/cloned/lib

@CrazyFlasher
Copy link
Author

It's not a workaround it my case. Currently I use local haxelib that downloads needed libs during ci build. If library is git, it deletes it and re-downloads, because I use --always flag to be sure that specified commit is taken. And .git folder that contains hostory is huge in some cases.
It would be cool if haxelib won't re-download lib from git, if specified commit is already present. Or update it in case of branch

@Gama11
Copy link
Member

Gama11 commented Feb 12, 2020

It sounds like you would be much happier with lix than haxelib. I guess you're using OpenFL though? Maybe you'll have to wait for openfl/lime#1381 then to be able to use it with lix.

@tobil4sk tobil4sk linked a pull request Jul 10, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants