Re: [CSCMail-Users] Can't locate MIME/Parser.pm

[Count Z. <cou...@cy...>]

Pavlos Parissis was overheard mumbling something about this on Thu, 04 Jan 2001
12:39:43 +0200

> i did it but it stopped with errors, correct me if i am wrong but this CPAN
will
> install tarballs and
> I do n't like this, i have already install gnome-perl in tarballs and i am
not
> going to install any other.
> As a result  i searched for rpms.

The reason to use Tarballs/CPAN and not RPMS for perl modules is simple (and is
exactly what is causing the following problem.)  Perl is fairly finicky about
the locations of it's files.  If the files are not in the right places it
cannot find them.  RPM's for perl modules will invariably get it WRONG.  Using
CPAN will always get it right!	For example, your site setup has @INC (the
"includes" directory list) set to tell perl to look in the following
directories for modules:

/usr/lib/cscmail
/usr/lib/perl5/5.00503/i386-linux
/usr/lib/perl5/5.00503
/usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005

Thats it... If a module is not in one of these directories, or beneath it, perl
cannot find it.

However, your Mail::Header module is in:
/usr/lib/perl5/site_perl

Well, that directory isn't in @INC, so perl doesn't look there for any modules.

To fix this, move the Mail directory from site_perl to site_perl/5.005

But of course, this invalidates the whole reason to use RPMS... Once you
manually move this file, you can no longer uninstall this module via RPM -e ...
Again, Perl is NOT RPM friendly... DO NOT USE RPMs to install Perl modules. 
Use the CPAN shell.  It will automatically install modules in the CORRECT
locations, it will automatically download modules, it will automatically
compile the modules for your system nice and cleanly, it will automatically
install module dependancies, it will automatically test module installation and
make sure everything is installed correctly.  CPAN performs the same functions
as RPM, but in a very Perl friendly manner.  I highly recommend that you
UNINSTALL (rpm -e) all of the perl modules that you have installed via RPM, and
re-install them via CPAN... Otherwise you are going to have nothing but
problems with any perl application you try to install and use.

Part of this is because there are not RPM's for every perl module, part of it
is because some of the RPMs you have installed are mdk rpms (and therefore
compliant with the Mandrake filesystem layout) and others are NOT mdk rpms (and
therefore live in some other location and perl cannot find them)

If you are insistant on using RPMs to install perl modules, you will always
have a hard time getting perl applications to run correctly, since you will
never end up with a consistant and correctly installed perl module tree.

-CZ