Forgot to include dbi-dev.

---------- Forwarded message ----------
From: Jonathan Leffler <[EMAIL PROTECTED]>
Date: Oct 25, 2007 5:08 AM
Subject: Re: -- How to transfer DBI/DBD binary.
To: "MEHTA, HARESH, ATTSI" <[EMAIL PROTECTED]>



On 10/24/07, MEHTA, HARESH, ATTSI <[EMAIL PROTECTED]> wrote:

>                 We are using tar file of DBD-Oracle-1.16 and DBI-1.50 to
> install DBI/DBD on our solaris server.
>
>
> "Everything should be made as simple as possible, but not one bit
> simpler."
>
> Albert Einstien



I must admit, I thought that quote was attributable to Albert Einstein...


-----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 24, 2007 2:27 PM
> To: MEHTA, HARESH, ATTSI; [EMAIL PROTECTED]
> Subject: RE: -- How to transfer DBI/DBD binary.
>
> I have not found a was to install it with out the compiler, what flavor
> of Solaris are you using?
>
> -----Original Message-----
> From: MEHTA, HARESH, ATTSI [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 24, 2007 9:15 AM
> To: [EMAIL PROTECTED]
> Subject: Ref:-- How to transfer DBI/DBD binary.
>
> All:
>
>                 I have installed DBI/DBD using gcc in our development
> solaris server. I want to install on production server but without using
> gcc or cc(compiler), Is there any way to transfer binary of DBI/DBD to
> production server??
>



You also said:

             I have installed DBI/DBD using gcc in our development
solaris server. I want to install on production server but without using
gcc or cc(compiler), Is there any way to transfer binary of DBI/DBD to
production server??


The easy way to do it is to insist that Perl will be in the same location on
both development and production machines - perhaps /usr/local/bin/perl or
perhaps somewhere else (I use /usr/perl/v5.8.8 at the moment, for example).
You then copy the entire perl directory structure from development to
production.

There are probably other ways to do it to -- this is Perl, after all, and
TMTOWTDI.  But I wouldn't bother.  Note that if you are careful, you can
have the software physically installed somewhere else (eg
/work3/perl/v5.8.8) but simply create a symlink at the 'official location'
that points to the 'physical location'.  I do that 100% of the time on my
development boxes; /usr/perl is a symlink to a random file system that has
space on the machine (such as /work3).

-- 
Jonathan Leffler <[EMAIL PROTECTED]>  #include <disclaimer.h>
Guardian of DBD::Informix - v2007.0914 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."

-- 
Jonathan Leffler <[EMAIL PROTECTED]>  #include <disclaimer.h>
Guardian of DBD::Informix - v2007.0914 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."

Reply via email to