On 05 Jun 2000 20:07:12 EDT, Lane Lester said:
>
> Steven Kordik said:
>
> > I only require Gtk and GtkHTML modules for CSCMail 1.9.x,
>
> Oh, crud. I never have been able to get that dadgum GtkHTML installed.
> I've
> given it two long serious attempts without success. I know that others
> have
> succeeded, and I know that others have failed. I hope the "secret"
> becomes
> known soon.
There are rpm's etc for GtkHTML 0.2 I am fairly sure... I seem to
remember a prospective CSCMail 1.9.x tester having some good luck
installing them.
> > out of the 1.7.x version. Consider 1.7.x to be in a feature
> freeze and
> > please use cvs to check it out and report any bugs to me...
>
> Have you been able to keep up with this list so that you know about
> the
> reformatting in the print routine and the failure to delete
> prontosending (I
> know that's not its right name)?
No, I was banned from the cs...@cs... list for a short while, and
missed any mails sent to that address since June 2nd I have not recieved.
I am setting up the new lists to be a bit more robust... For one thing
they are at sourceforge, and so list movement should stop, second, I am
setting up aliases for mail sent to cs...@cs... and
csc...@cs... so that even those messages should make it to
the new list... which is at csc...@li...
(btw: all the subscribers of cs...@cs... have been
auto-subscribed to the csc...@li... list, and the
old list has been desolved.)
Oh, and a few bugs in CSCMail 1.7.x have been fixed by me recently,
including the segfault in cscget when an invalid filter was
encountered...
be sure to use cvs to checkout the cscmail-1.7.x module from
cvs.cscmail.sourceforge.net
Instructions are available at http://sourceforge.net/projects/cscmail
The Pronto! folks have been notified of the issues I have fixed in
CSCMail 1.7.x, and can check the cvs logs at sourceforge, to see what
they need to do to fix these same bugs in Pronto!
I must admit however, that I will not be able to continue to make sure
that the Pronto! team is aware of all the issues I fix in CSCMail 1.7.x
as I do not have time to keep up with both CSCMail and Pronto! hehe I
would advise them to keep a CLOSE eye on the cvs logs for CSCMail 1.7.x
though, as nearly all of the code added to CSCMail 1.6.x (to turn it into
1.7.x) has bugs.
Anyway, the above was not a slam at the Pronto! developers... just that
as I look at the 1.7.x code, I see quite a few bugs... I will be fixing
them as I have the time, and the Pronto! team would be well advised to
track my fixes, since these bugs are (of course) forming the foundation
of Pronto! itself.
-CZ
|
