Help in installing DBD::Oracle module

[salluri]

Hi, I am trying to install DBD::Oracle module in the local (private)directory. Not the root directory (i don't have permission on the root) When i try to install the above module, it was saying that the DBI-1.52 is required. (Prerequisite) I installed DBI-1.52 from CPAN. the module installed fine with no errors. Used the following command to set the environment variable export PERL5LIB =/data/projects/marketsurv/perllib/lib/site_perl/5.8.3/ i686-linux-thread-multi The command ran successfully and Perl5LIB variable is set. i verified with the command perl -V and it is showing the @INC is set to /data/projects/marketsurv/perllib/lib/site_perl/5. 8.3/i686-linux-thread-multi (works fine) Now when i try to install DBD::Oracle with the following command, it is saying that DBI:1.42 is found (Somehow it is not looking at the local directory though the PERL5LIB is set) perl Makefile.PL PREFIX =/data/projects/marketsurv/perllib/lib/site_perl/5.8.3/ i686-linux-thread-multi ERROR DBI version 1.51 required--this is only version 1.42 at Makefile.PL line 19. BEGIN failed--compilation aborted at Makefile.PL line 19. Please help.. Thanks,

[leocharre]

I think this is too much work for a server you don't have root access to.

First and foremost- ask the admin to do it. Are you being ignored, refused? Consider another box (hosting provider/etc), or find a solution to your task that doesn't involve installing custom DBI drivers.

It's not a popular answer- but it is my honest suggestion- and in jaded experience, I think a good one.

I mean, is this like the last pebble to make your pyramid? How often will you be needing installs like this? Installing MySQL DBI drivers can be a little bit of a hassle even with root access, for example. You have to know that there are other funny non-perl deps.
So, this kind of thing can happen again with other modules- and waste a ton of your very valuable time.

[Thilosophy]

I think this is too much work for a server you don't have root access to.

I do not agree with that. Even when I have root access, I try to keep Perl projects self-contained, with all their dependencies locally (ideally on a per-project basis). If you start messing with site-perl, you will run into problems when you want different versions of the same module. It also makes it easier to revert back to a clean Perl install.

[stiller]

If you start messing with site-perl, you will run into problems

True enough, but that doesn't mean root (sysadmin) shouldn't install it. I think most sysadmins would be rather happy to get requests to install things per project rather than potentially breaking older commitments.

[almut]

You could trace what perl is doing under the hood. Something like

$ strace -efile perl -MDBI=1.51 -e1 2>&1 | grep DBI

This might give you a clearer picture of where it's actually looking, and what problem it's having with your private directory...

(BTW, that space in your paths is a cut-n-paste error, is it?)