On 29/06/2015 22:00, Grant Edwards wrote:
> After futzing around for a while installing and re-installing
> different versions of libftdi trying to get python support installed,
> I finally noticed that building libftdi python support requires swig.
> I didn't have swig installed and the ebuild apparently doesn't have it
> as a dependency.
> 
> Is the requirement to have swig installed when requesting python
> support for certain libraries something you're "just supposed to
> know", or should it be a dependency in the libftdi ebuild?
> 


The latter, and it's a bug that should be reported.

It happens often, mostly due to dev oversight (he already has the dep
installed so nothing gets triggered).

-- 
Alan McKinnon
[email protected]


Reply via email to