Libgpio would not compile (brought up errors about -lusb) until I updated libusb from libusb 0.7.1 to libusb 0.7.1-r1. See #25571. I guess the revision didn't matter, just that I had to re-emerge libusb. Perhaps libgpio should require the -r1 or greater, to ensure people have re-emerged. Reproducible: Always Steps to Reproduce:
emm, what is libgpio used for? i can't find any package in portage that depends on it ..
Ironically, it came up as dependency during KDE compilation since +gphoto.
ahh, thanks. it seems like kdegraphics needs it. kde guys, do you know why kdegraphics uses newdepends instead of DEPEND="" ? and also, can you confirm that kdegraphics/kamera really does use libgpio? because it doesn't appear in the configure.in: http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdegraphics/kamera/Makefile.am?rev=1.2&content-type=text/x-cvsweb-markup http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdegraphics/kamera/configure.in.in?rev=1.16&content-type=text/x-cvsweb-markup libgpio has been unmaintained for quite some time and libgphoto2 basically replaces all its functions.
the newdepends are there to maintain dependencies from within the eclasses. as for gpio, i don't see anywhere it's required. i'll remove it and see if it causes any problems.
I see a commit in kdegraphics' CVS log from last year that details the removal of the dependency on gpio as gphoto2 replaces it. The changes to kdegraphics in portage shouldn't pose any problems then. It may be worthwhile to just remove gpio from portage?
ok, i'll get around to removing libgpio then. thanks caleb.
caleb, can you remove media-libs/libgpio dep from kdegraphics-3.2.0_beta1?
ok .. kde guys removed the libgpio dep, so this is closable. deprecating libgpio in package.mask now
