[OGDev] Separating module install from guide install

[Kake L Pugh]

On Sat 12 Apr 2008, Dominic Hargreaves <dom at earth.li> wrote:
> 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>

OK, there is now a first pass at this in a branch named new-install-process.

It mostly works.  As of now, you can perl Build.PL, Build, Build test,
and Build install without having to answer a single question.  Once
you've done that, you can run openguides-install, answer the questions
there, and have it set up a guide for you.

Things that remain to be looked at include:

 - custom lib paths; haven't done this part yet
 - proper defaults wherever possible
 - installation of basic stylesheet
 - thorough checking that upgrades work properly (I think they mostly do)
 - Dom's request for an extra option to use symlinks for templates/scripts
 - ExtUtils::MakeMaker throws spurious warnings when we fix the shebang line
   (caused by our shebang lines not having options - not sure why we didn't
   get these warnings with Module::Build)
 - the code in openguides-install could probably be a lot neater
 - Debian stuff

Incidentally re basic stylesheet installation, does anyone mind if we
switch the default for "content above navbar in HTML" to "yes", and
make the stylesheet on this basis?

Kake