the gem install for sqlite3-ruby checks to see if swig (USE="ruby") is installed, if it is it changes the bindings it produces. http://code.whytheluckystiff.net/camping/wiki/BeAlertWhenOnSqlite3
Created attachment 99269 [details, diff] sqlite3-ruby-1.1.0-r1.diff patch sqlite3-ruby-1.1.0 to use a swig USE flag, if swig is used, it makes sure swig was compiled with USE="ruby"
Simply adding the use flag doesn't suffice, as having swig installed, but using USE=-swig, would built it using swig, but not storing the dependency.
Sorry, i didn't explain the patch properly, the patch also include this pkg_setup, does it not cover that? +pkg_setup() { + if useq swig && ! built_with_use dev-lang/swig ruby ; then + eerror "You must compile swig with ruby bindings. Please add" + eerror "'ruby' to your USE flags and recompile swig" + die "swig needs ruby bindings" + elif useq !swig && has_version dev-lang/swig && built_with_use dev-lang/swig ruby ; then + eerror "You have not specified 'swig' in your USE flags but" + eerror "swig is installed with ruby bindings. Either add" + eerror "'swig' to your USE flags or recompile swig without" + eerror "ruby bindings" + die "USE=\"-swig\" but swig was compile with USE=\"ruby\"" + fi +}
Or patch it so that it won't use swig if swig use flag isn't set
Created attachment 104134 [details, diff] new patch You'll need new gems.eclass from bug #158286
Created attachment 104135 [details, diff] sqlite3-ruby-1.1.0-no-swig.patch
This is fixed in CVS with version 1.2.1