[Chris Hofstaedtler] > The point of this bug was to get rid of the packages, not to > additionally introduce new ones.
My point of view is that discover was created with the purpose of proposing the relevant packages for installation based on the present hardware on a computer, and my suggestion to look into isenkram-cli come from the fact that this package was created to cover the same purpose. I also believe this goal is a valuable one to fulfill in Debian, and that dropping the feature is doing those installing Debian a disservice. Removing discover without adding a functional replacement is thus to me not an advantage, but a missed opportunity to bring better hardware handling to everyone currently having dsicover. I am not aware of any other packages than discover and isenkram in Debian providing information on which package to install for the relevant hardware in or connected to a Debian computer. Sadly discover have not been maintained for a while now, and thus in my biased opinion only isenkram provide the feature well today. d-i provide a reimplementation of isenkram-autoinstall-firmware at install time, while isenkram provide it also after installation, in addition to the more comprehensive handling of hardware related packages that are not firmware related. -- Happy hacking Petter Reinholdtsen
