It would be nice if DirectFB could use the same logic as for instance the xorg-x11 ebuild. That is, if it could use IUSE="video_cards_<foo>" and IUSE="input_drivers_<bar>" instead of just <foo> and <bar>.
Created attachment 86666 [details]
ebuild using video_cards_* and input_devices_*
no, IUSE_EXPAND takes care of that
Where does this IUSE_EXPAND magic happen? If you do emerge -vp and compare the results on the exsisting DirectFB-0.9.25.1.ebuild and my attached proposal, you'll see something like this:
[ebuild R ] dev-libs/DirectFB-0.9.25.1 USE="fbcon gif jpeg mmx mpeg png sdl sse sysfs truetype v4l v4l2 zlib -debug -fusion -static" 0 kB
My proposal gives:
[ebuild R ] dev-libs/DirectFB-0.9.25.1 USE="fbcon gif jpeg mmx mpeg png sdl sse sysfs truetype v4l v4l2 zlib -debug -fusion -static" INPUT_DEVICES="keyboard mouse -dbox2remote -dreamboxremote -elo-input -gunze -h3600_ts -joystick -linuxinput -lirc -mutouch -permount -serialmouse -sonypijofdial -wm97xx" VIDEO_CARDS="nvidia -ati128 -cle266 -cyber5k -i810 -i830 -mach64 -matrox -neomagic -nsc -radeon -savage -sis315 -tdfx -unichrome" 0 kB 
See the difference? The input devices and the video cards are explicitly shown just like in the xorg-x11 package. Also not that the proposed ebuild have changed from using INPUT_DRIVERS to INPUT_DEVICES, to keep consistent between xorg-x11 and DirectFB. This way you don't have to spesify both any more in /etc/make.conf.
not my problem
*** This bug has been marked as a duplicate of 101998 ***