I found out today that Microsoft has announced beta support for Xbox Cloud Gaming for Linux through Microsoft Edge for Linux.
We've talked off and on about having Edge added for people who are operating in Microsoft shops for business in the same way those who work in Google shops need Google Chrome, but I think this also makes it more compelling for us to have in our third-party repo set.
The only issue I see is that there's no AppStream repodata in the YUM repo: https://packages.microsoft.com/yumrepos/edge/repodata/
@jperrin, could you help out here so we can have that fixed?
Per a conversation with @jperrin, I've filed gh#microsoft/linux-package-repositories#4 to generally raise the issue of missing AppStream repository metadata and provide a basic suggestion on fixing it.
It seems this is now blocked on https://github.com/pulp/pulp_rpm/issues/2432.
There's probably not a whole lot more we can do here, other than ask the pulp developers to prioritize appstream metadata support?
It seems this is now blocked on https://github.com/pulp/pulp_rpm/issues/2432. There's probably not a whole lot more we can do here, other than ask the pulp developers to prioritize appstream metadata support?
It's the same as https://pagure.io/fedora-workstation/issue/283 (VS Code) it's not blocked on pulp, but rather on https://github.com/rpm-software-management/createrepo_c/issues/75
@jmracek FYI
I am sorry, there is no progress with https://github.com/rpm-software-management/createrepo_c/issues/75. The process of generating of metadata is awfully demanding therefore there is no way how to implement it as a default behavior. And if it is not default behavior then external tool can create metadata and modifyrepo_c can add metadata.
Clearly this is not currently possible. I'm going to go ahead and close it for now. Feel free to reopen when https://github.com/rpm-software-management/createrepo_c/issues/75 is fixed.
Metadata Update from @catanzaro: - Issue close_status updated to: Can't fix - Issue status updated to: Closed (was: Open)
See also VS Code issue #283
Login to comment on this ticket.