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

Support for installation of static exe files #194

Closed
tobiaskohlbau opened this issue May 19, 2020 · 9 comments
Closed

Support for installation of static exe files #194

tobiaskohlbau opened this issue May 19, 2020 · 9 comments
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Milestone

Comments

@tobiaskohlbau
Copy link

Description of the new feature/enhancement

In the go world it's very common to distribute static linked executables which are self contained and do not have any particular installer. I've read the spec and if I'm not mistake winget does not have support for this kind of applications.

Would be nice if winget would support such kind of apps. Somehow this is related to #182 and #140 .

Proposed technical implementation details (optional)

Put the executable into the correct installation folders. Maybe even allow the user to select the place and optional configurations files.

@tobiaskohlbau tobiaskohlbau added the Issue-Feature This is a feature request for the Windows Package Manager client. label May 19, 2020
@tobiaskohlbau tobiaskohlbau changed the title Support for installation of "plain" exe files Support for installation of static exe files May 19, 2020
@denelon
Copy link
Contributor

denelon commented May 22, 2020

This looks like a duplicate of #182

@denelon denelon added this to the Package Manager Backlog milestone May 23, 2020
@tobiaskohlbau
Copy link
Author

tobiaskohlbau commented May 23, 2020

You're right with the exception that this targets the executable itself without a decompression step. I opened this ticket to check if this kind of installation should get it's own InstallerType. As exe is already reserved for installable executables I could imagine two ways:

  1. New InstallerType for this kind of applications.
  2. Implicit supported by the zip type.

If the solution takes on the first option I could imagine that it's possible to share code with the zip implementation.

If you would like to move this discussions in the other issue we can close this. Thanks for your work!

@marcomorain
Copy link

👍 I'm looking for this feature to package the CircleCI CLI tool. The app is a single, static binary, that has no need for an installer/uninstaller, it's just an EXE that should be placed on the PATH when installed.

@koppor
Copy link

koppor commented May 24, 2020

Another example: wsay --> wsay.exe outputing text (Windows equivalent of macOS say)

@aetos382
Copy link

Should support renaming downloaded files before putting them in place.

@crpietschmann
Copy link

This would enable winget to be used to "install" Azure Bicep CLI which is only available as a stand-alone downloaded exe for the tool.

@denelon denelon added the Size-S label Sep 24, 2020
denelon pushed a commit that referenced this issue Oct 6, 2020
* Added PWA support spec

* Fixed typos

* Update and rename #194 - PWA Support.md to #164 - PWA Support.md

* Changed ManifestVersion to root level

* Update #164 - PWA Support.md

* Changed publisher name
@denelon
Copy link
Contributor

denelon commented Mar 4, 2021

This looks very similar to #182.

I think they are duplicates of each other.

I believe the ask is to have the ability to download the standalone program (in the form of a .exe) and make it available via the path so that a user can "install" it and use it.

If that is the case, I'd like to close this Issue as a duplicate, but I want to make sure everyone has the time to put their thumbs up on the other issue.

Are there any objections?

@denelon denelon added the Needs-Author-Feedback Issue needs attention from issue or PR author label Mar 4, 2021
@tobiaskohlbau
Copy link
Author

You're right with the exception that this targets the executable itself without a decompression step. I opened this ticket to check if this kind of installation should get it's own InstallerType. As exe is already reserved for installable executables I could imagine two ways:

  1. New InstallerType for this kind of applications.
  2. Implicit supported by the zip type.

If the solution takes on the first option I could imagine that it's possible to share code with the zip implementation.

If you would like to move this discussions in the other issue we can close this. Thanks for your work!

I'm totally fine with merging this issue into #182 if the supported case, of putting the executable without the extraction step, is supported by the solution of #182.

@ghost ghost added Needs-Attention Issue needs attention from Microsoft and removed Needs-Author-Feedback Issue needs attention from issue or PR author labels Mar 4, 2021
@denelon
Copy link
Contributor

denelon commented Mar 4, 2021

Yes, that is the intention of #182.

Anybody who has put their thumbs up on this issue should also put their thumbs up on #182.

@denelon denelon closed this as completed Mar 4, 2021
@denelon denelon removed this from the Package Manager v0.17.x milestone May 3, 2021
@denelon denelon added this to the v1.3-Client milestone Jun 21, 2022
@denelon denelon removed the Needs-Attention Issue needs attention from Microsoft label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests

6 participants