Ed Avis wrote:
> 
> >I'm developing a CGI application. It includes a perl module that
> >gets installed in the usual place, some command-line scripts that
> >should go in INSTALLSCRIPT and some CGI scripts that need to go into
> >a cgi-bin directory.
> >
> >What is my best strategy for handling installation?
> 
> The cgi-bin directory will be in wildly different places from one
> system to the next, so there's nothing you can do.  Besides, adding
> CGI programs to a live website is a security concern (I'm not saying
> your programs are insecure, just that it's a decision the
> administrator must make) so they should be copied in by hand.

  As for the cgi-bin directory being in different places, this
  would certainly require that the target directory location
  be specified. There are other aspects of this module that
  require hand-configuration. I agree that cgi programs present
  a security risk, but so do regular scripts to some extent.

> Just print a warning message listing the CGI programs that should be
> installed.  If you are thinking of a particular system, and a
> particular place to put the CGIs, then it would probably be best to
> keep them out of the Makefile.PL (which is supposed to apply to all
> systems) and just have a shell script which runs make and then copies
> a couple of files with cp.

  When you say "Just print a warning message," is there a standard
  way to do this as part of (or upon completion of) 'make install'?

   -Norton

Reply via email to