sigma-file-manager
sigma-file-manager copied to clipboard
Automatically publish `.msix` packages in `/releases`.
My rationale is available at https://github.com/felixrieseberg/windows95/issues/221.
Consider supporting the developer on Patreon to increase priority of all your issues, get access to private discord and other rewards.
Patreon page: https://www.patreon.com/sigma_file_manager
You can install the app with winget install sigma
I will publish v1.5 update today. I think, it will need a few days to update in the winget system
I'm not sure what you mean by "allow proper management". Please feel free to re-open the issue if it's still relevant
@aleksey-hoffman, winget
is indeed a package-manager, but dissimilarly to all alternative package-managers, does not enforce a standard package-format. This means that management of software installed by it is comparatively difficult.
I can build a MSIX package, but it will be unsigned
Do you know if unsigned build is suitable for winget
?
@aleksey-hoffman, please remember that winget
is merely the package-manager, and is consequently similar to all but snap
in that it supports repositories.
I do not believe that the package-manager prevents installation of unsigned packages. However, I believe that the default msstore
or winget
repositories mandate this, especially msstore
.
I suggest that you attempt to submit it via "https://github.com/microsoft/winget-pkgs/issues/new?assignees=&labels=Help-Wanted%2CPackage-Request&template=package_request.yml&title=%5BPackage+Request%5D%3A+".
I am thankful for your assistance.
I don't fully understand the issue, mate.
It's already available on winget
and it seems it works as intended.
What would the MSIX file change?
@aleksey-hoffman, I believe that to explain it any more I risk unnecessarily duplicating what the relevant documentation of MSIX already explains better than I am able to, so I suggest that you read it. If you understand how your current installer operates, you should very quickly be able to ascertain how native manipulation via PowerShell, uninstallation without remnant, and management via unified interfaces and methods are desirable.
If I have incorrectly interpreted your response, I apologize: you appear to desire additional rationale for why support for MSIX is desirable, but I may well have incorrectly interpreted your response.
Any technical support is probably best received by creating a pull-request at the relevant WinGet manifest that replaces the current installer's URI with a new one for the MSIX package. The moderators shall assist you with any problems relevant to the packaging at there.
I am thankful for your assistance.