Feel free to leave the local description as a bonus, but rename the actual USE flag to the global USE="libffi" which has been the standard flag name for this feature since always (see sys-devel/gcc for eg)
Recent (>=1.5.0) versions of nokogiri no longer support ffi as a method, so this USE flag will disappear from the package altogether once we stable the next version.
By the way libffi is NOT the correct flag for Ruby packages. That's because they don't use _libffi_ but they use the FFI technique, through the ffi extension, which for JRuby is implemented through JFFI and not libffi.
(In reply to comment #2) > By the way libffi is NOT the correct flag for Ruby packages. That's because > they don't use _libffi_ but they use the FFI technique, through the ffi > extension, which for JRuby is implemented through JFFI and not libffi. yeah, you are right. perhaps we should actually rename the global 'libffi' to 'ffi' and convert everything to that :/ a bit of a job, but end result should be more flexible... (In reply to comment #1) > Recent (>=1.5.0) versions of nokogiri no longer support ffi as a method, so > this USE flag will disappear from the package altogether once we stable the > next version. thanks, so that will handle this bug then.
