Emerging sqlite3-ruby with the 'swig' use errors out during build if swig is not built with the 'ruby' USE flag. Can't v2 ebuilds throw this warning earlier? Reproducible: Always
(In reply to comment #0) > > Can't v2 ebuilds throw this warning earlier? > I guess you mean EAPI 2. Theoretically, yes, we could show that warning earlier. But since EAPI 2 is only supported by Portage versions in testing, we can't apply that change to the stable ebuilds. Expect a change at the earliest at the next version bump or the time Ruby 1.9.1 hits the tree, whichever comes first. At that time, sqlite3-ruby's swig USE flag is going to disappear, too, since non-swig builds are deprecated. If that "problem" is still a severe issue to you, you can try out the sqlite3-ruby ebuild from the Ruby overlay (for instance via layman), which is already EAPI 2 and includes the change you proposed.
Closing this bug as we can't fix it in the current tree without a stable portage that supports EAPI 2. Fixed versions using EAPI 2 are already in the ruby overlay and will be moved into the tree when possible.
EAPI-2 is now stable.
As far as I know the ruby use flag for swig should not have been needed. In fact, the latest swig no longer has these USE flags. The check for this got remove in Feb 2009. Also, in Apr 2009 the ebuild got changed to EAPI=1 so that we can encourage people to turn on the swig USE flag. Closing this bug since all issues seem to have been covered.
