[Raphaël Hertzog] > I noticed that the modaliases file mentions "virtualbox-ose-guest-x11" but > nowadays it should be "virtualbox-guest-x11".
Note, the preferred way to maintain the list of hardware-package mappings is by adding AppStream metadata into the individual packages. This way the information is available everywhere, not only for isenkram. See <URL: https://wiki.debian.org/AppStream/Guidelines#Announcing_supported_hardware > for instructions on how to do this. I update the modaliases file included in the isenkram package using the data available from appstream, but hope to drop the modalises file completely in the future once every mapping there is also available using appstream. So far, 97 such mappings are missing. :( This is the mapping you talk about in this case: Package: virtualbox-ose-guest-x11 Modaliases: unused(pci:v000080EEd0000BEEFsv*) Is the PCI ID a good marker? Anyway, I added this to work with both new and old package names: Package: virtualbox-guest-x11 Modaliases: unused(pci:v000080EEd0000BEEFsv*) It will be included in the next upload. > Also that suggestion is only applicable if you have Xorg installed. > You might want to have virtualbox-guest-dkms (or -utils) as default > package selection and somehow suggest the -x11 only if you have Xorg > (not sure if that's something that is possible in isenkram). I can only map from hardware to package, there is no conditionals involved at the isenkram level. Is there some way to use different hardware markers for this? > It would be nice if you could review packages to be installed > for other virtualization technologies: > - there's qemu-guest-agent for qemu > - maybe there are others that you are missing I'm happy to adjust the mapping file on request, but am unlikely to have capacity to do a review on my own any time soon. -- Happy hacking Petter Reinholdtsen
