Make available via scoop, choco, and winget.

[koppor]

Once gg can be on PATH and there is a kind of gg config, it would be nice if gg.cmd could be installed via scoop, chocolatey, or winget.

With this, I can tell people to do following (after a clone of the JabRef repository and installing github-cli and gg.cmd)

• gh pr checkout 12252
• gg.cmd

Alternative: In the installation part, I could instruct them to download gg.cmd to the root of JabRef's repository. I just wanted to have some more options 😅.

Side note: WinGet seems to support .zip-based "installatations": microsoft/winget-cli#140

[eirikb]

Once gg can be on PATH and there is a kind of gg config, it would be nice if gg.cmd could be installed via scoop, chocolatey, or winget.

With this, I can tell people to do following (after a clone of the JabRef repository and installing github-cli and gg.cmd)

* `gh pr checkout 12252`

* `gg.cmd`

Alternative: In the installation part, I could instruct them to download gg.cmd to the root of JabRef's repository. I just wanted to have some more options 😅.

The idea of gg was to just add it to the repo, such as with gradlew.
In JabRef it could just replace gradlew.
Unless I misunderstand what you mean.

[eirikb]

I'm not sure if I can make git work - at least on Windows it has a lot of install options (git bash) etc?

Roughly thought: Doesn't need to be the full git. Just portable or a minimal git supporting "the most important" commands 😅

True. Will see if I can make it work

[koppor]

On Windows, the portable is "just" 63 MB :). One unfortunatly cannot use the 43kb git.exe standalone - one really needs the other files.

I think, you will like gitoxide more. However, there is no support for recursive clone of git submodules.

Binaries at https://github.com/GitoxideLabs/gitoxide/releases/tag/v0.44.0.

Update I think, it is OK to omit submodules for now if gix is the best option 😅

---

>cargo binstall gitoxide
 INFO resolve: Resolving package: 'gitoxide'
 WARN The package gitoxide v0.44.0 (x86_64-pc-windows-msvc) has been downloaded from github.com
 INFO This will install the following binaries:
 INFO   - ein.exe => C:\Users\koppor\.cargo\bin\ein.exe
 INFO   - gix.exe => C:\Users\koppor\.cargo\bin\gix.exe

[eirikb]

On Windows, the portable is "just" 63 MB :). One unfortunatly cannot use the 43kb git.exe standalone - one really needs the other files.

I'm not too worried about 63MB to be honest. Java is like 400MB. It adds up and that's bad I understand that, but it's the same with node_modules etc. Think I have argued sizes before.

And with -g support in gg it is really not a big deal, if one opts to use that.

[koppor]

I'm not too worried about 63MB to be honest. Java is like 400MB. It adds up and that's bad I understand that, but it's the same with node_modules etc. Think I have argued sizes before.

I think, it was #77 (comment) :)

But its good. Then I can stop looking for ideas 😅. I was about to write a jbang-driven git clone. Not possible with libgit2 (e.g., git24j/git24j#161).

And with -g support in gg it is really not a big deal, if one opts to use that.

I hope that it works without explicit -g 😅 (We are discussing at #77 (comment))

---

Update: Thanks to JGit Command Line Interface, I don't need git support. jbang enables it.

[koppor]

Updated my howto (https://github.com/JabRef/user-documentation/pull/569/files?short_path=c063175#diff-c06317529fc3d3260624a8d46014409f5b4acb39ac9298b8f53b2991f9ac8b9e)

./gg.cmd jbang https://github.com/JabRef/jabref/blob/main/.jbang/CloneJabRef.java JabRef

Future work: jbang git@jbangdev - but this does not use the latest jgit version (jbangdev/jbang-catalog#45) and I am not sure whether I should give "control" about the used jgit versoin out of my hands ^^

[eirikb]

Doing some housekeeping in old discussions.

I keep landing on the same answer as back then: gg is meant to sit in the repo, like gradlew. If people have to install it first, it stops solving the thing it was made for.

But I think what you are really after is not having to type ./gg.cmd all the time, and that is #247 - a .gg directory of shims you add to PATH once, per project, nothing installed globally. That one I like, and it is still open.

I like having "gg" on my own machine, and that's what I set up most places now.
I've also enabled "-u" to handle "gg".
I know there were discussions about gg vs gg.cmd and so on, but I now consider the "cmd" mostly as ".exe". It was added for CMD support initially.

Closing this one in favour of #247.