I see the site_perl directory now, thanks.
To fill you in on what exactly I'm doing: The script accepts periodic data
or text input files from a vendor (for a specific database), parses it to
fit our specifications, and outputs a text file for a bulk-insert into a SQL
database.
I think I've go
on 10/1/02 10:39 AM, [EMAIL PROTECTED] purportedly said:
> I think the clear answer is that putting modules and data into User space
> was a mistake. And that using directories in "System space" and absolute
> pathnames will cure my headaches.
By and large.
> Scream if I still don't get it...
>
Thanks to all for their help.
I think the clear answer is that putting modules and data into User space
was a mistake. And that using directories in "System space" and absolute
pathnames will cure my headaches.
Scream if I still don't get it...
(Script saved in /usr/local/bin)
#!/opt/perl/bin/
On 9/27/02 9:12 AM, "Tim Grant" <[EMAIL PROTECTED]> wrote:
> A philosophy question...
>
> For no particular reason, I keep my Perl scripts in user space
> (/Users/grant/bin/perl). The scripts work with directories elsewhere in my
> user space. These scripts get deployed to other machines and are
on 9/27/02 8:12 AM, [EMAIL PROTECTED] purportedly said:
> A philosophy question...
>
> For no particular reason, I keep my Perl scripts in user space
> (/Users/grant/bin/perl). The scripts work with directories elsewhere in my
> user space. These scripts get deployed to other machines and are ru
A philosophy question...
For no particular reason, I keep my Perl scripts in user space
(/Users/grant/bin/perl). The scripts work with directories elsewhere in my
user space. These scripts get deployed to other machines and are run by
different users.
Is there a good way to tell Perl about the u
