Robert Nicholson wrote:
So how is it possible then to arrange the installation of the each version of
SA into a separate directory but yet still share a common site_perl amongst
these versions?
The scripts like sa-update etc seem to assume that SA is installed into the
site_perl and not a separate directory for this version of SA only.
This is because sa-update etc choose to override @INC by assuming that the only
site_perl stuff that's relevant is that that's relative to where SA is installed
please correct me if I'm wrong.
am I expected to edit the ".raw" files and add the necessary "use lib" lines?
What I've done here to allow multiple SA install trees is to rely on the
system Perl and packaging system for everything outside of SA itself,
then install SA (using a wrapper script for consistency) explicitly
defining PREFIX, SYSCONFDIR, and LOCALSTATEDIR to keep the config and
rule updates all confined to the same tree. I haven't had any trouble
with SA finding the wrong internal libs in this setup, nor with it not
finding systemwide modules.
The install wrapper is itself packaged, and depends on all of the
packaged modules we have in our standard SA configuration.
Which OS are you on?
perl -V:installvendorlib and perl -V:installsitelib should tell you
where Perl thinks modules should be found (as well as just 'perl -V');
so far as I'm aware SA shouldn't *override* those, but add to them.
-kgd
