-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add modalias support #59
Comments
We don't have to do that to get the task of porting software-properties done, but it certainly would be nice :) |
Everything is already there in appstream-generator to support this. The respective packages just need a metainfo file specifying modaliases. You can also query for components that support a given modalias using |
On Wed, Mar 07, 2018 at 04:20:16AM -0800, Matthias Klumpp wrote:
Everything is already there in appstream-generator to support this. The respective packages just need a metainfo file specifying modaliases.
See https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-provides (modalias YAML field exists as well) as well as this Debian Wiki entry: https://wiki.debian.org/AppStream/Guidelines#Announcing_supported_hardware
Can we generate this from the apt metadata instead of / as well as
making pkgs provide the metainfo file?
…--
Iain Lane [ [email protected] ]
Debian Developer [ [email protected] ]
Ubuntu Developer [ [email protected] ]
|
I guess so (don't we do a similar hack for GStreamer plugins?), although I would of course very much prefer any such solution to be just a stopgap to proper metainfo files. |
@ximion Historically, in RPM distributions, the mod-aliases have been part of rpm I'm not sure whether we've added too many of these other than for the NVIDIA driver to metainfo... |
In order to migrate the driver finding in Ubuntu to PackageKit, we think it makes sense to use AppStream to do that. I think what we have to do for that is
Modaliases
field, which looks like this:Modaliases: nvidia(pci:v000010DEd000005E7sv*sd00000595bc03sc*i*, ...)
Does that sound about right?
The text was updated successfully, but these errors were encountered: