Date:  Sun, 17 Nov 2019 06:12:51 -0800
From:  Neil Waldhauer <neil at blondeguy dot com>
Subject:  Re: [pmm2-U] PMMail 3.24 beta 1

On 11/16/19 10:08 pm, dougb007 at telus dot net wrote:
> On 2019-11-15, at 16:36:41, Neil Waldhauer wrote:
>> A beta build of PMMail for OS/2 version 3.24 is available on the
> FTP
>> site.
>>
>> ftp://pmdevpub:anyname%40anydomain at ftp.os2voice dot org/
>>
>> PMMail is built with GCC 4.9.2 and requires libcx. To satisfy this
>> requirement, you can use Arca Noae Package Manager or yum.
> The package
>> to
>> install is named libcx.
>>
>> The filename of the beta version is pmmail-3-24-00-2373.wpi. This
>> version
>> is time-limited, and operation will degrade after the limit is
> reached.
>> To reset the limit, reinstall the release version.
>>
>> Please give feedback to the PMMail users list.
> Okay, I finally found a bit of time for this. So far, this is what I have
> found:
>
> PMMUTIL.EXE is not included. PMMUTIL.ICO is included.
> (PMMUTIL replaces the badly named Migration tool).
>
> Since PMMUTIL.EXE is not included, it cannot run for the update,
> and therefore fails to remove the obsolete files (such as
> DRCTL017.* which may be in ....\PMMail\bin). Not having the file
> present probably causes the failure to create the PMMail Utility icon
> too.
>
> DRCTL is another package that needs to be installed by ANPM
> (RPM/YUM). Note that there are probably many copies of
> DRCTL017.DLL on your system, which may need to be removed
> before installing from ANPM (RPM/YUM). You may also have older
> copies (like DRCTL016.DLL), which should be left for the programs
> that need them. The DRCTRL package should be installed BEFORE
> attempting to install, or update, PMMail. There should be only ONE
> copy of DRCTL017.DLL, and it should be in
>  at unixroot/usr/lib/drctl017.dll. If you insist on managing that stuff
> without using RPM/YUM, it can be anywhere in your LIBPATH, but
> don't blame PMMail, when something doesn't get done properly.
>
> Some details need attention, but the program seems to work okay.
>
> More when I find more time...

The gory details probably belong on the programmer's list, but the 
details of the installer are to me a grey zone, part end-user and part 
developer. So I'll leave this discussion here.

First, I have to say thanks to Doug for the helpful comments.

I looked in trunk\PMMail\Makefile, and it still is trying to make 
MigratePMM.exe.

Is it just a simple name replacement MigratePMM.exe --> PMMUTIL.EXE? I 
think not. Below that, there is an entry for MigratePMM.exe: ... that 
builds MigratePMM.exe

I see you have PMMutil.RES in version control. It isn't really right to 
have a binary in version control, but it isn't any worse than having 
MigratePMM.RES in version control, so I'm OK with it for now.

I propose to change the Makefile by substituting PMMutil for MigratePMM. 
I know you are busy, so I think that's all that would be needed to get 
PMMutil.EXE into the WarpIN installer.

As for adding DrCtl (note capitalization, it's important) I will add 
that to the RPM/YUM installation instructions. As for cleaning up 
whatever the user has, I don't want to automatically clean up what the 
user has manually added. If PMMutil.Exe can clean that out of the old 
BIN directory, that is OK.

I hope these two changes should address all the problems you listed. As 
for users manually installing prerequisites, I intend to help them in 
the future with a distribution that contains all prerequisites and does 
not depend on RPM/YUM.

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