The current stable ruby-dbi ebuild misses oracle USE flag. Therefore support for Oracle databases cannot be enabled for ruby-dbi. Reproducible: Always Steps to Reproduce: 1.check the current stable (0.1.1) ruby-dbi ebuild 2.inspect the ebuild for any Oracle database support 3.Notice there is no support there Actual Results: No Oracle support there Expected Results: An use flag for the ruby-dbi packages to enable Oracle database support corrected ebuild is attached to this bug
Created attachment 174308 [details] Updated ebuild with oracle use flag added Also tested the newest ruby-dbi package (0.4.1), but that version is completely different and doesn't seem to have support for Oracle anymore. Anyhow that version didn't work with some metasploit modules MC developed, which is the reason why I updated this ebuild. (http://www.metasploit.com/users/mc)
Thanks for submitting your enhancement. Assigning to maintainers.
As far as I can tell ruby-dbi 0.4.1 still has Oracle support, at least according to the documentation, but it looks like all the dbd packages got split out to different packages. DBD::OCI8 seems to be provided by the ruby-oci8 package. Did you also test ruby-dbi-0.2.0? This version is newer and contains bug fixes compared to 0.1.1, so I'd much rather fix 0.2.0 for now and work towards stabling that.
(In reply to comment #3) > As far as I can tell ruby-dbi 0.4.1 still has Oracle support, at least > according to the documentation, but it looks like all the dbd packages got > split out to different packages. DBD::OCI8 seems to be provided by the > ruby-oci8 package. I made an ebuild for version 0.4.1 of ruby-dbi and also installed the latest ruby-oci8 version (1.0.3), but I was not able to get it working. When I switched back to version 0.1.1 it was working right away. > Did you also test ruby-dbi-0.2.0? This version is newer and contains bug fixes > compared to 0.1.1, so I'd much rather fix 0.2.0 for now and work towards > stabling that. I've just done a test with ruby-dbi-0.2.0 and that version is working fine as well. See attached ebuild. I also included an ebuild for the latest version of ruby-oci8 (1.0.3).
Created attachment 174638 [details] ruby-dbi-0.2.0-r1, Oracle use flag added
Created attachment 174640 [details] ruby-oci8-1.0.3.ebuild
I've added dev-ruby/ruby-0.2.0-r1 based on your version (but minus the one typo) :-) Also cc'ing Troy Bowman, the maintainer of dev-ruby/ruby-oci8, for the updated ruby-oci8-1.0.3.ebuild (and possibly he can also shed some light on the ruby-dbi 0.4.1 issues. Finally, note that there is a 0.4.1 version of ruby-dbi in the ruby overlay.
(In reply to comment #7) > I've added dev-ruby/ruby-0.2.0-r1 based on your version (but minus the one > typo) :-) > > Also cc'ing Troy Bowman, the maintainer of dev-ruby/ruby-oci8, for the updated > ruby-oci8-1.0.3.ebuild (and possibly he can also shed some light on the > ruby-dbi 0.4.1 issues. Yeah, ruby-oci8 needs a version bump. The ebuild is very simple and bumping it up a version is trivial. It looks like Erwin already did it and attached it to this bug. The only thing I don't like about his version is that the SRC_URI is hard-coded, and we might be able to use the rubyforge mirror://rubyforge/ for the SRC_URI. As for ruby-dbi, the DBD::OCI8 interoperability is an upstream problem, and thus would be best handled by the http://ruby-oci8.rubyforge.org/ team. In my experience, I've never been able to get ruby-dbi to work completely reliably with ruby-oci8, even in the older where it seems to work at first. The last time I tried ruby-dbi with DBD::OCI8 (almost a year ago), ruby-dbi didn't handle cursors (prepared statements) and variable bindings appropriately, and only worked with the simplest of statements. I've resorted to just using ruby-oci8 sans ruby-dbi for now until the dbi and oci8 wizzes hammer out the problems.
I now see that the ruby-oci3-1.0.3 ebuild switches to the gem format. I'd rather keep it as a normal ruby ebuild instead, but I can't test the new version since I don't have Oracle installed.
I'll build and test ruby-oci8-1.0.3 with a normal ruby (non-gem) build when I get into the office in a couple weeks. I'm on vacation for the holidays and I don't do Oracle for fun at home.
Created attachment 177122 [details] ruby-oci8-1.0.3.ebuild using rubyforge mirror Here's a version that uses rubyforge and non-gem. Now version bumps should be as simple as changing the filename. I've installed it and it appears to be fine for my stuff.
I've now added the ebuild to Gentoo CVS. Thanks Erwin and Troy!
