Hello, > I don't think you can install that automatically, the location of CGI > scripts varies so much between systems and is normally tied in to the > URL it's served at. Anyway installing a CGI script on a public server > has security implications and so it ought always to be done by hand.
Well, my idea is to install all project related files into one central place, i.e. /usr/local/$(NAME)-$(VERSION)...including all project specific perl modules. Then I ask the admin to insert two statements in the Apache configuration: Alias /$(NAME) /usr/local/$(NAME)-$(VERSION)/htdocs ScriptAlias /$(NAME)/cgi-bin /usr/local/$(NAME)-$(VERSION)/cgi-bin Therefore I don't care where the systems CGIs normally are located and, as you also mentioned, the CGI installation isn't done automatically for security reasons. > >some textual documentation, some images and XSL-stylesheets located > >in an htdocs-directory and some binaries. > > These are all a case of some 'files' that need to be copied > 'somewhere'. And as far as I can tell there is no support in > MakeMaker to simply say 'this file goes there'. > > For my own application I have much the same problem, and I ended up > writing lots of extra MakeMaker code to add targets to the generated > Makefile. I added a 'plaindoc_install' target to put things under > .../share/doc/ and I made this a dependency of the normal 'install' > target. thanks a lot...that was exactly what I was looking for...I built my own Makefile.PL with yours as a guide and it works great ;-) Certainly the problem has been discussed on this list before but wouldn't it be a good idea to support generic installation with MakeMaker as well. As I did in my version of Makefile.PL the user (of MakeMaker) could specify categories of files (i.e. htdocs) with their source, INST and INSTALL locations. The mechanism already exists in MakeMaker for PM and EXE_FILES, so it might be possible to use a similar but more generic approach... Well, if anyone needs another example for a Makefile.PL you can of course also have a look at my version, which will be available in the upcoming release of the ZoneMaster project on Sourceforge.NET. (http://www.zonemaster.org) regards...Andy
