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
URI scheme should support listing alt ids #183
Comments
|
@hughsie Do you have an opinion on this? |
|
Not a fan of the |
Obviously, yes. But if there are no objections to the thing in general, I would add it to the next release. Problem is that using the new scheme might break existing tools unless they explicitly already extract the path component of the URI. |
Urgh, then it's an "API break" which probably needs a different URL prefix. |
|
@hughsie Purely by the specification alone, this isn't an API break because the apps were supposed to use the path component as component-ID. Since there was no other URI component so far though, it was fine to not care about the specifics here and just take the whole URI. |
...this passes. What problems did you see? |
|
Very interesting! I just launched it with |
|
This was overdue, so it's in now. Discover still chokes on these URLs, so it may be a good idea to update it first ;-) |
|
Doesn't seem to "choke" on 5.17? |
|
In that case I blame the ancient KDE/Qt components on Debian Testing. For some reason the Debian KDE team didn't update the KDE components for a really really long time now. |
|
Just implemented this in Discover, should be available in Plasma 5.18 LTS. |
The metadata format now supports providing previous ids via
<provides>unfortunately the URI format doesn't.It would be good if the format supported alternative ids being passed. e.g. something like
With the id renaming in place the target system evaluating the appstream URI could have any of those ids depending on how old it is.
The text was updated successfully, but these errors were encountered: