With media-plugins/vdr-xineliboutput it should be possible to build the package without pulling in vdr and its dependencies. Xineliboutput has remote frontends, that can be used with vdr on an another computer. There is a simple workaround. First emerge xine-lib and then vdr-xineliboutput with --nodeps option. I tested this with vdr-xineliboutput-1.0.0-pre5 and xine-lib-1.1.2-r2. Simply adding an use flag for vdr dependency and removing vdr-plugin from inherit didn't work, so I have no patch to propose at this moment.
That would require changes to the eclass to disable DEPENDENCIES per use-flag.
Created attachment 101848 [details] Ebuild for client-only install of xineliboutput Here it an ebuild I have used to install client-only parts of xineliboutput. I didn't make this myself, credits should go to phintuka@hut.fi, author of xineliboutput. This solves the problem for me.
I think this could be done by extending the existing ebuild with no changes to the build system: add a "client" and a "server" use flag which are enabled by default. The server dependencies should only be required with "server" use flag. This enables the old behaviour with no changes plus a new client-only build with "-server" use flag.
Fixed up from vdr-xineliboutput-1.0.4 you can use USE="vdr" or USE="-vdr" to handle this.
