Hello, Messing around with my HP printer, the `hp-scan` command provides a traceback: ``` Traceback (most recent call last): File "/usr/bin/hp-scan", line 40, in <module> import scanext ModuleNotFoundError: No module named 'scanext' ``` This is both confusing and unhelpful, as it doesn't really clue me in that I forgot to emerge net-print/hplip with USE=scanner Can this binary be removed if USE=-scanner? It will at least remove the command that will never run successfully. I believe a "Why isn't this command on my system?" is more helpful than "why is this command buggy / giving me a module not found?", especially without python knowledge. Thanks, -- Marco Sirabella
It is possible to remove hp-scan if scan support is disabled. However I think this should be done upstream. I guess this is the case for more tools than just hpscan. Also in this case I think it is really straightforward that if the ebuild has a scanner USE flag scanning features only work if it is enabled.
Makes sense to me, I'll forward it along to upstream > Also in this case I think it is really straightforward that if the ebuild has a scanner USE flag scanning features only work if it is enabled. Disagree with this though, not everyone is looking at the use flags of every package they install, checking the use flags might be a reasonable step in debugging the traceback issue but there shouldn't even be a "debugging" step for commands that will never run successfully.
Well then bring it upstrwam.
