is unofficial installers allowed #38681
-
|
hello if a program doesnt have a installer are you allowed to make a unofficial installer to put it on winget? (Edit: i dont know if this is a answer or not #35008) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
If the project doesn't have an People are allowed to make forks of a particular project with their own changes to the application (as long as they follow the original project's licensing), but they aren't allowed to pass it off as an "official" version of the original project. Some publishers also doesn't allow you to repackage their own installers without permission from the publisher for security, legal, privacy, and malware reasons. Most people prefer to download from official sources, instead of unofficial sources because for unofficial sources, it's hard to verify its authenticity (InstallerSha256 would be different), even if you haven't modified any of the publisher's binaries. You will either have to wait until WinGet supports more "installer" types (i.e.
Author who created that discussion wanted to build their own installer outside of NSIS/InstallShield/Inno/MSI/etc for their own program. which is a bit different from repackaging someone else's project into a installer for Windows. |
Beta Was this translation helpful? Give feedback.
-
|
another question. if i get permission from the creator of the program to make a installer with inno/advanced installer? |
Beta Was this translation helpful? Give feedback.
-
You can help support their project by contributing to it; such as making modifications to their CI/CD pipelines to create an MSI installer. You can take a look at Git for Windows's Work-In-Progress MSIX PR to get an idea on how you can do this. Any other way, such as getting permission from the publisher to create your own installer based on NSIS or other repackage tools, is still considered a "repackage" of the original project which isn't allowed to be submitted to the WinGet Community Package Repository. If you want to submit repackaged installers, you could perhaps create your own private repository using the REST API or create a GitHub repository with local manifest files, which would allow you to create your own packages without having to contribute to the WinGet Community Package Repository. |
Beta Was this translation helpful? Give feedback.
-
|
ok thx for answering |
Beta Was this translation helpful? Give feedback.
If the project doesn't have an
EXEor anMSIor anMSIXversion, then no, you won't be able to.People are allowed to make forks of a particular project with their own changes to the application (as long as they follow the original project's licensing), but they aren't allowed to pass it off as an "official" version of the original project.
Some publishers also doesn't allow you to repackage their own installers without permission from the publisher for security, legal, privacy, and malware reasons.
Most people prefer to download from official sources, instead of unofficial sou…