Date: Thu, 21 Nov 2019 20:38:51 -0800 From: Neil Waldhauer Subject: Re: [pmm2-U] PMMail 3.24 beta 2 On 11/21/19 08:05 pm, dougb007 at telus dot net wrote: > On 2019-11-21, at 18:11:45, Neil Waldhauer wrote: > > This is getting confusing, so I dropped a lot of the older stuff... > >>>> I think bogofilter, stunnel and tnef might be the external > programs >>> we still supply. >>> >>> BogoFilter 1.25 has been released (we are now at 1.24). See >>> >>>> https://bogofilter.sourceforge.io/NEWS >>> We probably should look into learning how to build that. The > current >>> version was built by Dave Saville, who passed away some years >>> ago. >>> >>> STunnel seems to have some more updates that we probably >>> should get. See: >>> >>>> https://www.stunnel dot org/ >>> Paul Smedley has done a couple of them for us. Again, we > probably >>> should look into building it ourselves, since it seems that the >>> functions are not likely to be incorporated into PMMail, any time >>> soon. >>> >>> I don't know where TNEF comes from. Readme.OS2 credits: >>> --------------------------- >>> Mentore Siesto >>> Pisa, Italy >>> mentore.siesto at alice.it >>> ---------------------------- >>> I have no idea if there is a newer version. >>> >>>> Neil >> Thanks for the list of items. I agree about the need to build >> bogofilter. Maybe not for this release, but long term, we should > have >> it, and it should probably be in the VOICE RPM repository, once > that is >> operational. > I agree. Not for this release, we already have too many changes, > and that can be confusing if somebody has a problem. > >> I just uploaded Beta 3. That should create the PMMail utility icon >> correctly. > It looks like the PMMail Utility icon is now updated properly. I did > have some sort of problem with PMMutil.exe, that I haven't tried to > analyze, yet. That may be something left over from a previous > failure. I still need to do a new install, which wasn't completing > because of the previous PMMutil problems. > > I still have a build problem that I need to resolve (I think I am > missing something), but that is okay as long as you can build it > successfully. > > QUESTION: Are you using the Watcom build, or the old method? > Have you decided which way we will go, for the longer term? > >> The installer no longer checks for DLLs, but it still is >> checking for PMMail 2.x. I don't know if that is important -- we > launch >> PMMutil.EXE at the end of the install even if we do not find PMMail > 2.x. > > Actually, it IS doing the DLL checks. It just doesn't show the > summary of the results. I will look at updating the WIS to remove > some, or all, of that stuff. I have some sample WIS files, from Alex > Taylor, showing how to determine if the user is using RPM/YUM, or > not. Once I figure that out, we can change the WIS to offer to run > YUM, or pop up a message that the user needs to manually add the > required packages (which needs to be documented). That can wait > for the next release. > > It is important to do the check for PMMail 2.x, so PMMutil knows > what version it is dealing with when the user does an update. I need > to do some serious testing (including doing an update from PMMail > 2.x), but I probably can't get to that until Saturday, at the earliest. > PMMutil.exe also does some clean up when PMMail 3.x is found (it > runs silently), so it does need to run when PMMail 3.x is updated. > >> The installer still installs any ASpell packages it happens to see. I >> guess there is no harm in leaving those in. > That still works, but users should be discouraged from doing it that > way. For now, it won't hurt to leave them in. Removing them is > pretty easy. What we really need, is to be able to uninstall those > packages, using the WarpIn installer, then offer to run YUM to > install the RPM/YUM version. > >> I'm going to look at doing release notes. Are there Mantis entries I >> should include? > Probably. It has been some time since we started this last update, > and I will need to review what was done. Unfortunately, some of it > may not be documented properly. > > We should probably remove the older WPI files from the FTP site > too, before somebody gets themselves tied up in knots. Well, the DLL checks are gone in beta 3. I think it's better to keep the WarpIN installer as simple as possible, and document anything else in a readme. When the installer finds an old PMMail, it displays it on the page, but the information is not passed on to PMMutil. So we might as well removed that code from the installer as well. If the user wants to de-install the old Aspell, that is easily done in WarpIN. That would make a good help/readme item. I'll begin reviewing the documentation. I will clean up the FTP site. Thanks, Doug, for reviewing and testing PMMutil. best regards, Neil -- Neil Waldhauer neil at blondeguy dot com www.blondeguy dot com Expert consulting for OS/2 Warp, ArcaOS and eComStation ----------- To unsubscribe yourself from this list, send the following message to MajorMajor at os2voice dot org unsubscribe PMMail2User end