522
522
until you run the post-install
523
523
<filename>checksetup.pl</filename>
524
524
script, which locks down your installation.</para>
526
<para>Lastly, you'll need to set up a symbolic link to
527
<filename>/usr/bonsaitools/bin/perl</filename>
528
for the correct location of your Perl executable (probably
529
<filename>/usr/bin/perl</filename>).
530
Otherwise you must hack all the .cgi files to change where they look
531
for Perl. This can be done using the following Perl one-liner, but
532
I suggest using the symlink approach to avoid upgrade hassles.
536
<para><quote>Bonsaitools</quote> is the name Terry Weissman, the
537
original author of Bugzilla, created
538
for his suite of webtools at the time he created Bugzilla and several
539
other tools in use at mozilla.org. He created a directory,
540
<filename>/usr/bonsaitools</filename> to house his specific versions
541
of perl and other utilities. This usage is still current at
542
<ulink url="http://bugzilla.mozilla.org/">bugzilla.mozilla.org</ulink>,
543
but in general most other places do not use it. You can either edit
544
the paths at the start of each perl file to the correct location of
545
perl on your system, or simply bow to history and create a
546
<filename>/usr/bonsaitools</filename> and <filename>/usr/bonsaitools/bin
547
</filename> directory, placing a symlink to perl on your system
548
inside <filename>/usr/bonsaitools/bin</filename>
554
perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm syncshadowdb
557
Change <filename>/usr/bin/perl</filename> to match the location
558
of Perl on your machine.
1185
1150
url="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource">ScriptInterpreterSource</ulink>
1186
1151
directive in your Apache config, if you don't do this, you'll have
1187
1152
to modify the first line of every script to contain your path to
1188
perl instead of <filename>/usr/bonsaitools/bin/perl</filename>.
1153
perl instead of <filename>/usr/bin/perl</filename>.