Let's change USE=libffi to more generic USE=ffi so it will cover also eg. ffcall. DESCRIPTION could be simple:
"Enable support for Foreign Function Interface" -- cut -- 1. "libffi" (dev-java/jamvm): use dev-libs/libffi to call native methods 2. "libffi" (dev-python/pygobject): Enable support to connect to signals on python objects from C. 3. "libffi" (gnustep-base/gnustep-base): Use dev-libs/libffi instead of dev-libs/ffcall 4. "libffi" (sys-devel/gcc): Build the portable foreign function interface library 5. "libffi" (sys-devel/llvm): Add support to call arbitrary external (natively compiled) functions via dev-libs/libffi 6. "ffi" (app-i18n/uim): Enable support for virtual/libffi 7. "ffi" (dev-ruby/nokogiri): Use the Foreign Function Interface library (as provided by dev-java/jruby or dev-ruby/ffi depending on the implementation) rather than building a C extension to wrap around the libxml/libxslt interfaces. Note: JRuby always uses the FFI interface as native extensions are not supported. --- cut --- Any objections... ?
