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

[FEATURE] Windows installer and Package management etc. Winget / Choco #175

Closed
tom8zds opened this issue Jun 11, 2024 · 13 comments
Closed
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@tom8zds
Copy link

tom8zds commented Jun 11, 2024

need installer for windows or upload to package management like winget or choco, portable release not convinent when upgrade

@love-linger love-linger self-assigned this Jun 11, 2024
@love-linger love-linger added enhancement New feature or request help wanted Extra attention is needed labels Jun 11, 2024
@lgranie
Copy link

lgranie commented Jun 18, 2024

I have made a scoop manifest
ScoopInstaller/Main#5923

@LouieTian0209
Copy link

Agreed. Having a standalone installer for Windows would be a lot better, especially since there are already deb and rpm packages for Linux.

@gadfly3173
Copy link
Contributor

gadfly3173 commented Jun 27, 2024

I tried to create a manifest for a winget package: gadfly3173/winget-pkgs@d35d484 , but encountered some issues:

  • Portable package installed via winget is not able to create shortcuts on the Desktop and Start Menu, while open them through the command line throws a System.DllNotFoundException: Unable to load DLL 'libSkiaSharp' or one of its dependencies. There is no issue when opening the application directly from the winget installation location or by using the shortcuts located in %LOCALAPPDATA%\Microsoft\WinGet\Links.
  • winget lacks the ability to automatically detect new release versions, requiring either manually submitting a PR to the winget-pkgs repository or using wingetcreate.exe to automatically initiate the process and then manually filling out the PR content.

I think a standalone installer is helpful to improve the upgrade experience, which is also the form of installation of most GUI tools in winget.

@ZaLiTHkA
Copy link

just FYI, searching through the Scoop "apps" list page, I found a user bucket that includes Sourcegit: https://scoop.sh/#/apps?o=false&q=sourcegit

I have made a scoop manifest ScoopInstaller/Main#5923

unfortunately, this PR was closed with a request to reopen it in the "Extras" bucket, but I don't think this has happened yet.


not to imply that a Winget package is not required, just a note to say that an installation path is currently available through Scoop.

@love-linger
Copy link
Collaborator

The description for this app in https://scoop.sh/#/apps?o=false&q=sourcegit is Native Kubernetes desktop client..

I've created a new package request to ScoopInstaller/Extra bucket. Hope they can add it to the offical bucket.

@ZaLiTHkA
Copy link

The description for this app in scoop.sh/#/apps?o=false&q=sourcegit is Native Kubernetes desktop client..

yeah, I did notice that, it does actually install Sourcegit though..

I've created a new package request to ScoopInstaller/Extra bucket. Hope they can add it to the offical bucket.

awesome.. hopefully that gets a little more visibility to this awesome Git client! :) there aren't many Linux options that come anywhere close to Sourcegit.

@tom8zds
Copy link
Author

tom8zds commented Jul 1, 2024

what about a quick and simple approach by innosetup, just pack the portable into installer

@love-linger
Copy link
Collaborator

what about a quick and simple approach by innosetup, just pack the portable into installer

There is no point in providing an installer if you can't solve the problem of automatic upgrades within the installer.

@LouieTian0209
Copy link

what about a quick and simple approach by innosetup, just pack the portable into installer

Only if it won't overwrite existing configs and histories. If innosetup installer can only overwrite/replace project files and leave configs and histories alone, then it makes sense to have it offered as an option for release.

@love-linger
Copy link
Collaborator

what about a quick and simple approach by innosetup, just pack the portable into installer

Only if it won't overwrite existing configs and histories. If innosetup installer can only overwrite/replace project files and leave configs and histories alone, then it makes sense to have it offered as an option for release.

But I can't find any advantages that compares to the portable way.

@love-linger
Copy link
Collaborator

@love-linger
Copy link
Collaborator

image

Now, users can install this app via

winget install SourceGit

Note: If you have run self-build SourceGit that based on develop branch after tag v8.18, please do NOT install from this way. It's because that after v8.18, the settings of repository has been moved into the repository's git dir. The preference.json modified by it can not be used by the older version, such as release v8.18

@love-linger
Copy link
Collaborator

It's installed SourceGit as a command-line tool. You should run it from the console or Win+R at the first time. Then you can add it to taskbar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

6 participants