in reply to Re: Re: CGI file writing
in thread CGI file writing

Hi mcogan1966,
How I normally get around this is either create a module .pm which can be included in any dir in @INC and called with use Foo::Bar;. Or a library .pl called with require /path/to/baz.pl;.

You would then make filenames and paths variables which are read in from the file making it portable throughout many systems without having to touch the script itself.

Replies are listed 'Best First'.
Re: Re: Re: Re: CGI file writing
by mcogan1966 (Monk) on Oct 29, 2003 at 17:02 UTC
    Actually, I found a different solution.
    Since I know that the server structures are going to be identical from my development system to the production system (as designed by the network admin who built this whole thing), I tried doing the relative path using ../../var/logs. Sure enough it works properly. Now, I don't have to worry about what system it's on.

    Yeah, I know, it's not exactly the best way to do it for overall portability. But that's not the situation here, and it's not like this code is ever going to go out into the wild. It's strictly for this client, for use in just this system (as is always the wonderful part about writing code for GovCo).
[reply]
[d/l]

In Section Seekers of Perl Wisdom