Comment 20 for bug 1031468

I have activity on this bug at launchpad.net

Three final notes/bugs here:

1) The hplip ebuild is likely not upgrading the binary plugin when hplip ebuilds are upgraded on the the users' systems. After manually deleting all printers within CUPS, emerging/compiling hplip with default USE Flags (X hpcups libnotify policykit qt4 scanner snmp -doc -fax -hpijs -kde -libusb0 -minimal -parport -static-ppds") or (+qt4 -static-ppds) and doing "hp-setup -i 192.168.1.27", XSane now works. I think the recompiling with default USE flags was over-kill, but I did anyways as it was the easiest method. I'm pretty sure now, hplip is not upgrading the binary plugin and am just awaiting confirmation.

This bug should likely be renamed to "hplip doesn't upgrade binary scanner plugin on upgrades".

2) hplip requires Python 2 and not Python 3 for using hp-setup. See https://bugs.launchpad.net/hplip/+bug/891080. The hplip ebuild should, at the very least, notify users to "eselect python set (version 2)" before attempting to use hp-setup. (Possibly only when they're installing for a device using this binary scanner plugin.) Archlinux appears to have submitted a bug and/or it is filed on launchpad (2011-11-16) also without any fixes as of yet. Another place for documenting would be wiki.gentoo.org/hplip, but the site seems to be down currently.

This is likely an easy thing to do without having to open a new bug.

3) hp-uninstall should likely be removed from hplip as it removes itself, overriding the Gentoo Portage package manager! In other words, who knows what it removes (ie. rm -rf) when uninstalling! There's also an hp-upgrade script, but I'm unsure what this does. Personally, think this package is getting to be a package maintainer's worse nightmare. ;-)