in reply to DBI ?...moving module files manually...no shell or telnet access

You can't just move DBI.pm around. It depends on a binary that gets installed and is specific to the particular version of Perl that is installed.

You'll either have to get the admin to install it, or you'll need some sort of shell access. If neither of those are available, you're out of luck.

-- Randal L. Schwartz, Perl hacker

  • Comment on •Re: DBI ?...moving module files manually...no shell or telnet access

Replies are listed 'Best First'.
Re: Re: DBI ?...moving module files manually...no shell or telnet access
by Kanji (Parson) on Jun 05, 2002 at 01:35 UTC
    You'll either have to get the admin to install it, or you'll need some sort of shell access. If neither of those are available, you're out of luck.

    Not sure if your definition of 'shell access' extends beyond an interactive session with telnet or ssh, but in many cases, all you really need is the ability to execute arbitrary scripts on the target machine ... something you probably already have in the form of CGI!

    #!/bin/sh

echo "Content-Type: text/plain"
echo ""

(
  gzip -cd Module-2.1.tar.gz | tar xvf -

  cd Module-2.1 

  perl Makefile.PL LIB=~/lib

  make
  && make test
  && make install
) 2>&1

    [download]

    Sure it can be a pain, but it works.

        --k.


[reply]
[d/l]

      Let's see if I understand this...

      You're saying that I can write an install script that would take the tar.gz file and make (build) it on the host machine and install itself to a folder of my chosing? I'm assuming that I just d/l and copy the tar.gz into my cgi-folder so that the script can access it?

      This would be uber-kewl...if that is what you mean (and if I have access to do it). Can this be done with all modules?

      Otherwise, please slap me into place and lead me down the path of Perl module installation enlightenment.

      Much-o grass-y-ish

      ======================
      Sean Shrum
      http://www.shrum.net

[reply]
Re: •Re: DBI ?...moving module files manually...no shell or telnet access
by S_Shrum (Pilgrim) on Jun 05, 2002 at 23:04 UTC

    Not nessecarily true...

    I had posted these modules manually previously and had them working.

    Since then I have *updated* (upgrade -install) my modules locally and now have the problem on my external site after reposting them to the site.

    ======================
    Sean Shrum
    http://www.shrum.net

[reply]
      You've never done that with DBI: I'd bet the rent money on it.

      Perhaps you're thinking of some other pure-perl module, but DBI from day one has always had a binary shared-object component to it.

      -- Randal L. Schwartz, Perl hacker

[reply]

        Hmmm...maybe your right but it seems odd that while I am under Windows and my host is under FreeBSD that it worked in the past...maybe they had the binary installed for that server...would explain why it doesn't work now...that they put me on a fresh server.

        Well then, what do I need to do in order to get DBI to work. How do I go about getting a build for my hosts server Linux OS?

        Thanx for the help so far.

        ======================
        Sean Shrum
        http://www.shrum.net

[reply]

In Section Seekers of Perl Wisdom