[ic] Does IC install extra stuff?

[Gert van der Spoel]

> -----Original Message-----
> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
> users-bounces at icdevgroup.org] On Behalf Of Grant
> Sent: Tuesday, August 18, 2009 1:17 AM
> To: interchange-users at icdevgroup.org
> Subject: Re: [ic] Does IC install extra stuff?
> 
> >> >> # ls /usr/local/interchange/lib
> >> >> Bundle    DBI.pm  HTTP        LWP.pm  Parse        Storable.pm
>  Vend
> >> >> dbixs_rev.pl    lwptut.pod
> >> >> Business  Digest  Image       MIME    Roadmap.pod  TASKS.pod
>  WWW
> >> >> hints.pl        perllocal.pod
> >> >> DBD       File    IniConf.pm  Net     Set          Term
> >> Win32
> >> >> install_lsb.pl  relocate.pl
> >> >> DBI       HTML    LWP         OLE     Spreadsheet  UI
> auto
> >> >> lwpcook.pod
> >> >>
> >> >> Is that a whole slew of perl modules?  Will IC use those instead
> of
> >> >> the ones I installed into the system via portage?
> >> >
> >> > I suppose that depends on the order in your perl lib path?
> >> >
> >> > CU,
> >> >
> >> > Gert
> >>
> >> OK, but should all of that have been installed during a make install
> >> in which I'm trying to keep it as minimal as possible?  Is that the
> >> expected function of make install here?  I just don't have much
> >> experience with it.
> >
> > Well I think this has also been installed when you installed the
> > kitchensink.
> > I can only say that I have noticed this behavior, it does not happen
> to
> > everybody, but I have not had enough time to investigate this further
> ...
> >
> > CU,
> >
> > Gert
> 
> Is there a way to figure out if IC is using any of the perl modules in
> /usr/local/interchange so I might be able to delete them?  Could 'make
> install' have installed anything outside of /usr/local/interchange?

You installed Bundle::KitchenSink already before you finished your IC
install right?
Then my assumption is that if you would remove those perl models from
/usr/local/interchange that things should still work.

Then again, my 2nd theory is that if you have Interchange installing those
modules under /usr/local/interchange/  then the Perl that you used to
install interchange was not able to find these modules. Or the test in order
to find these modules is broken in the Interchange installation process ... 

Are you using a stock Perl, or your own compiled Perl?  There might be the
key to this. I use a self compiled Perl and if you do too then this might be
the reason why these things end up in /usr/local/interchange ... But that is
just a theory and that could mean that the installation process has a
certain issue with determining if all modules are available ... 

And if you are not on a production environment then the first thing I would
try is to move all of those modules away from /usr/local/interchange,
restart the kitty and see if she will still purr ... If you are only having
production that might be a bit of a crash & burn experience for some of the
visitors in those exciting 5 minutes ...   (so 'move all of those modules =
zip -r -9 myiclib.zip /usr/local/interchange/lib/ ... then whackallmodules ,
restart, check if it still plays, if not unzip that myiclib.zip and restart
... ) ... 

Warranty until the end of this e-mail ... 
Like about ... here :)
CU,
Gert