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

Sure it can be a pain, but it works.

    --k.



In reply to Re: Re: DBI ?...moving module files manually...no shell or telnet access by Kanji
in thread DBI ?...moving module files manually...no shell or telnet access by S_Shrum

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.