> [EMAIL PROTECTED] wrote:
>>> Why do you bother yourself with installation of Mail::Domainkeys?
>>> It is not needed by QT at all!
>> Thanks for the info, should this installation be removed from the perl
>> install scripts then??
>
> Sorry for long delay in answer, I've been off from list busy with some
> urgent duties. Could you please explain in details what methods do you
> use to install QT on a fresh CentOS4.x installation?
>
> --
Alexy,

Not a big deal, hope you got what you needed to taken care of.  I just
performed a minimal install of Centos 4.4, downloaded the install scripts
from the QT site, and followed the installation instructions line-by-line.
 Only, I executed each script command by itself to watch, see and learn
from the results.

It seems, at least on my install, that perl-HTML-Parser is never
installed, and the Spamassassin rpm fails without yum installing it first
(I noticed it is not in the deps script, and installing it from CPAN did
not resolve the issue).

What the original post concerned was during the execution of the perl
modules script, I had to force install Crypt::OpenSSL::RSA before I could
get Mail::Domainkeys to install.  Since you had stated the
Mail::Domainkeys is not needed by QT, I was just wondering if it could be
eliminated from the perl script.

However, the HTML-Parser issue is really perplexing me. I've looked over
the list, and cannot really find anyone else having this issue (or maybe
everyone just yum'ed it like I did and went on with the install).  Do you
think this is a Centos 4.4 issue?? I'm going to grab a copy of 4.3 and try
again to see if the same type things happen.

Everyone on this list is really great, and the feedback is excellent. 
Just give me your thoughts, and I'll post the results from the 4.3 test.

Robert Van Dresar
Airplexus, Inc.

>
>



---------------------------------------------------------------------
     QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to