> > Hi, Jeff, > > Quoting Jeff Urlwin <[EMAIL PROTECTED]>: > > > One thing to keep in mind is that you *should* get your > binary built > > modules from the same location. So, if you want DBD::Oracle, make > > sure you get DBI from my site. > > this is what bothers me. First of all, note that the current > release is build 806. I *think* that the modules will be > upwards compatible, but your sentence above makes me > suspicious. Besides, I think it is unlucky to be bound to > your vesion of DBI. For example, it might prevent me from > using my own version of DBD::DB2, DBD::mysql or whatever.
Right. And if anyone asks for a database, I'll try. My issue may be licensing, but MySQL shouldn't be a problem. I have a copy of DB2, but haven't tried building against it. Sybase may be an issue. I should have already built DBD::CSV, but haven't gotten around to it. > > I would propose that you instead try to get DBD::Oracle into > the ActiveState repository. (Note that DBD::ODBC already is > there.) From my experience with DBD::mysql I know that I could NOT agree with you more. However, ActiveState has *specifically* dropped it due to what I consider percieved licensing issues. They have claimed (and it's been posted here) that they are violating Oracle's licensing policies by distributing a binary. I think, while they may be technically/legally correct, I'm sure it's not something Oracle would even consider. Hence, for the last two months, I've been *loosely* trying to get someone in Oracle to even call me back about it. The Online forums suggest you talk to Oracle Sales. The Oracle Sales suggest you talk to the Partner program, etc... > > a) The ActiveState people are interested in adding important > database drivers to the repository and > b) they have the (quite understandable) expectation that the > driver can be built automatically on their system. > Yes, and they've cut it off due to the above, which is what prompted me to do this in the first place. > In the case of DBD::mysql, things went as follows: I posted a > question on the perl-win32 list and receieved a response from > Jan Dubois (of > ActiveState) that they have been unable to do an automatic > build. After exchanging several emails (including some bug > fixes in the test suite from Jan, which showed up on Windows > only) they were able to add the driver to their repository. I've had a similar experience, although mine was more frustrating because it was while they were having problems with their automated build process. Jochen -- I agree with you, but until someone gets Oracle to write it to ActiveState or ActiveState works it out with Oracle, I'll do the best I can. It's been frustrating that Oracle is one of the more popular DBDs (I use it myself on a daily basis, in production) and I can no longer get a build for it on machines where I have a license for Oracle, but no compiler. The PPM tool is great, as long as the repository has every module ever built. (Ok -- I'll be realistic, not all the modules will build on Win32, etc). It's a large task and I'm only trying to make a stop-gap solution for DBI only -- which is daunting enough for a busy person. Jeff
