|Pathologically Eclectic Rubbish Lister|
MS Frontpage, _vti_cnf directories and perllibsby skazat (Chaplain)
|on Jul 18, 2006 at 18:02 UTC||Need Help??|
skazat has asked for the wisdom of the Perl Monks concerning the following question:
I'm having some peculiarities with servers that run Frontpage extensions, and perl cgi apps that have lib files.
I'm not a Frontpage guru, but the program seems to like to create directories called, "_vti_cnf" all over the place - I'm assuming as a cache or a place to put some sort of meta data for the FP program itself.
Fairly ugly. But a weird thing also happens - these directories become part of @INC. File store in the, "_vti_cnf" directories hold the same name as the files they're meta-data'ing/caching - but with different content - which means, if the copy of these files try to get used in a perl app, perl will tell you there's all sort of errors.
The workaround is to just move the app-specific perllib out of wherever the app (in this case, a CGI script) is located, usually in the cgi-bin, and locate it in, say, the home directory.
Here's a diagram of the directory structure:
cgi-bin ---- script.pl ---- lib (dir) -------- Config.pm -------- Brain.pm -------- _vti_cnf (dir) ------------ Config.pm
For whatever reason, the copy of, "Config.pm" in the, "_vti_cnf" dir will be used/required etc, even though the program could look like this:
So, is there some sort of workaround, either telling perl not to use the Front Page created directories, or something in Frontpage to tell it to layoff the cgi-bin?
I develop a program (Gnu), that gets installed all over the place, so I have no control over the environment it gets installed in.
Thanks for your help!