On Sat 12 Apr 2008, Dominic Hargreaves dom@earth.li wrote:
If I understand correctly the essence of this is http://search.cpan.org/src/KAKE/CGI-Wiki-Kwiki-0.59/bin/cgi-wiki-kwiki-insta...
Kind of. I was mostly thinking of the CGI::Wiki::Kwiki install itself - i.e. installation of the CGI::Wiki::Kwiki modules. The way that works is that it installs the cgi-wiki-kwiki-install script and the CGI scripts in the normal bin directory, and it installs the templates under the normal Perl module hierarchy. That way, you have your install script in your path, and perl knows where to find the templates when the install script asks it for them (in the same way as it knows where to find the modules). I've got this working to the point where the OpenGuides modules will install with no manual intervention.
To my mind, this is copying too much - the templates and CGI scripts oughtn't be copied for each guide. The templates and CGI scripts can just live in a standard place (the Debian packages put them in /usr/share/openguides/templates and /usr/lib/cgi-bin respectively) and if needed, the "install directory" for the guide can contain symlinks to the CGI scripts.
Yes, this can be an option in the openguides-install script.
For the time being, I won't be committing this to OpenGuides svn trunk. I can commit it in a branch if someone would like to send me absolutely idiot-proof instructions for doing so.
svn cp https://urchin.earth.li/svn/openguides/trunk \ https://urchin.earth.li/svn/openguides/branches/<your-branch-name>
svn co https://urchin.earth.li/svn/openguides/branches/<your-branch-name> \
<branch-working-dir-name>
cd <branch-working-dir-name> [hack hack hack] svn commit
Thank you!
Kake