-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[Package Request]: FilesCommunity.Files.Preview
#166364
Comments
Note
Blocking-Issue
This issue should be closed as "not planned". |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as resolved.
This comment was marked as resolved.
I have already given a link for preview builds #150390 (comment) |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@Dragon1573, #166364 (comment) has been reverted per files-community/Files#15973 (comment), so the installer URI is now an |
It seems the |
Based on the PR your missing the dependencies and the arm64 version that Files supports. You can see the one for stable #150504 |
Dependencies and |
.appx and .msix are basically the same. You can change the extension from one to the other and things will generally work. Difference is that .appx is older. Older versions of the OS don't know MSIX (I think those are already out of support), and there are probably features that are only supported in MSIX and not APPX, but the package format is the same. A bundle (either MSIX or APPX) contains a collection of individual packages. Those can be variations of the same package, just for different architectures. Or they can be resource packages with the strings/assets for different locales. A .appinstaller file is an XML file that helps the OS manage auto-updates and dependencies for an MSIX package/bundle. It lists a URI for a main package and its dependencies, so that the OS can install the dependencies before the main package. It also lists a URI where a new version of the .appinstaller file can be found, and the OS can use that to check for updates. Without changes to winget, you can already add a package for which you have a .appinstaller by just opening it in a text editor and extracting the package URI to use in winget.
@Dragon1573, It isn't true that it cannot be installed unattended (but it's true that winget doesn't support it). You can do |
@florelis, that's brilliantly comprehensive. Thank you. If you'd rather not submit one yourself, I've added that as an answer to the cited SU question: |
Hello @RokeJulianLockhart, This package appears to require user interaction to install. This package is blocked until support for interactive installer search filtering is implemented in: Be sure to add your 👍 to the issue to help raise the priority and avoid posting "Me too!" messages to respect those who have subscribed to the issue. Template: msftbot/blockingIssue/interactiveOnlyInstall |
Hello @RokeJulianLockhart, This issue has been identified as requiring a fix from a third party or external repository. Since there has been no recent activity on this issue, it will be automatically closed. Template: msftbot/noRecentActivity/areaExternal |
I don't believe so see #150504 (comment) |
How can we help?
I would like someone else to build the manifest.
Please read and ensure the following
Please provide the following information
FilesCommunity.Files.Preview
3.6.0.0
, from https://github.com/files-community/Files/releases/tag/v3.6 (per https://github.com/files-community/Files/releases/latest).The text was updated successfully, but these errors were encountered: