On 13/01/05 16:13 -0600, Todd Ross wrote:
> Hello,
>
> I'm interested in instructions for a best practices approach to
> upgrading a Kwiki installation from 0.36 to 0.37. Hopefully, this would
> apply to future versions as well.
>
> I run my Kwiki installation in a shared hosting environment. I
> installed Spiffy, IO::All, Template::Toolkit, Spoon, and all of the
> Kwiki modules into <home_dir>/local_perl.
>
> perl Makefile.PL PREFIX=<home_dir>/local_perl
> make
> make test
> make install
>
> I then have to modify index.cgi and add the following 'use lib' statements:
>
> use lib '<home_dir>/local_perl/lib/perl5';
> use lib '<home_dir>/local_perl/lib/perl5/site_perl';
Both index.cgi and /usr/mumble/bin/kwiki have the line:
use lib 'lib';
That means if you have your modules installed in the lib directory of your
kwiki installation, then you don't need to change anything. In your case just
do:
ln -s <home_dir>/local_perl/lib/perl5/site_perl lib
Then you can leave index.cgi alone.
> The only problems this approach causes is that index.cgi gets rewritten
> everytime I do a kwiki -update, so I always have to re-add those lines.
> Removing the write bit on the file causes kwiki -update to fail. Is
> there a better way to handle this?
Hmm. I should make the installation module skip files that it can't write to.
Thanks for the good idea.
> How should I upgrade those modules? Is it as simple as just installing
> over the existing modules with the new versions? Should I reinstall the
> newest versions of all of the modules everytime I want to upgrade my
> Kwiki installation? Meaning, should I delete local_perl and recreate it
> every time?
>
> Once the modules are upgraded, is the Kwiki upgrade as simple as running
> kwiki -update from the Kwiki install location?
Yes.
I should also point out that if you have a lib directory then
kwiki -install Kwiki::Mumble
will download the latest Kwiki::Mumble from CPAN and install it in your lib
directory. (And will run kwiki -update, of course)
> Are there any
> configuration differences that I should be worried about? How would I
> know in the future if the configuration has significantly changed or if
> modules that I use have been removed from the base distribution?
I will probably add a
kwiki -upgrade
that will bring everything up to date, no matter what version you are on. Stay
tuned...
Cheers, Brian
