Date: Wed, 20 Nov 2019 13:04:37 -0800 From: Neil Waldhauer Subject: Re: [pmm2-U] PMMail 3.24 beta 2 This is a multi-part message in MIME format. --------------554FCE86BD815DB036F59135 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 11/19/19 07:57 am, dougb007 at telus dot net wrote: > On 2019-11-19, at 06:39:32, Neil Waldhauer wrote: >> On 11/18/19 09:14 pm,dougb007 at telus dot net wrote: >>> On 2019-11-18, at 15:15:33, Neil Waldhauer wrote: >>>> A second 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/ >>> Testing a new install: >>> >>> There is an error in the WIS file. Line 329 should be: >>> CREATEOBJECT="REPLACE WPProgram|PMMail >>> Utility||EXENAME=$(1)\BIN\PMMUtil.EXE;PAR > AM >>> ETERS=$(1);STARTUPDIR=$(1)\BIN;OBJECTID= e> >>> ;" >>> but that may still be wrong. It is supposed to REPLACE the old >>> Migration tool icon with the PMMail Utility icon (same icon, > different >>> words). >>> >>> Looking in the package, PMMutil.exe is not present. >>> MigratePMM.exe is present. It appears that PMMutil.exe is not > being >>> created, for some reason (I never understood how that happens). >>> MigratePMM.exe is probably left over, and may need to be > removed >>> manually from the bin directory, before building. >> Are you sure PMMUtil is not present? I see the syntax error in the >> CREATEOBJECT line, and that will be fixed. MigratePMM.EXE > was still >> there, I guess you are right about removing it manually. The WPI > did >> deliver PMMutil.EXE and update the object parameters, even with > the >> syntax error. Oddly, the name of the object did not change. I will >> experiment and see if I can get that to work. Perhaps the syntax > error >> caused the problem. >> >> I will create a beta 3, but for now, I need to know if others can run >> PMMutil.exe, even though its icon is named wrong. >> >> best regards, >> >> Neil > Using WPIView, I see the icon, but not PMMutil.exe, in the WPI > installer. I get the same thing, when I try to build PMMail myself. I > can manually build PMMutil.exe, in my DrDIALOG setup. The icon > is static, and is simply placed in the \bin directory under version > control. > > After doing DOMAKE, PMMutil.exe should be in > ...\pmmdev\trunk\PMMail, but it is not, so there is no file to copy to > \bin. The Makefile in the PMMail directory has been updated between beta 1 and beta 2. The latest copy does copy PMMutil.EXE to the install\BIN directory when I make the install target. The WIS file is checking a number of libraries that are now managed by RPM/YUM. It might be better to skip these checks and just list the libraries that PMMail needs so people can use ANPM or RPM/YUM to install them. I can make the changes and see if anything stops working. I think bogofilter, stunnel and tnef might be the external programs we still supply. Neil -- Neil Waldhauer neil at blondeguy dot com www.blondeguy dot com Expert consulting for OS/2 Warp, ArcaOS and eComStation --------------554FCE86BD815DB036F59135 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

On 11/19/19 07:57 am, dougb007 at telus dot net wrote:

On 2019-11-19, at 06:39:32, Neil Waldhauer wrote:

On 11/18/19 09:14 pm, dougb007 at telus dot net wrote:

On 2019-11-18, at 15:15:33, Neil Waldhauer wrote:

A second 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/

Testing a new install:

There is an error in the WIS file. Line 329 should be:
CREATEOBJECT="REPLACE WPProgram|PMMail
Utility|<PMMailFolder>|EXENAME=$(1)\BIN\PMMUtil.EXE;PAR

AM

ETERS=$(1);STARTUPDIR=$(1)\BIN;OBJECTID=<PMMailMigrat

e>

;"
but that may still be wrong. It is supposed to REPLACE the old
Migration tool icon with the PMMail Utility icon (same icon,

different

words).

Looking in the package, PMMutil.exe is not present.
MigratePMM.exe is present. It appears that PMMutil.exe is not

being

created, for some reason (I never understood how that happens).
MigratePMM.exe is probably left over, and may need to be

removed

manually from the bin directory, before building.

Are you sure PMMUtil is not present? I see the syntax error in the
CREATEOBJECT line, and that will be fixed. MigratePMM.EXE

was still

there, I guess you are right about removing it manually. The WPI

did

deliver PMMutil.EXE and update the object parameters, even with

the

syntax error. Oddly, the name of the object did not change. I will
experiment and see if I can get that to work. Perhaps the syntax

error

caused the problem.

I will create a beta 3, but for now, I need to know if others can run
PMMutil.exe, even though its icon is named wrong.

best regards,

Neil

Using WPIView, I see the icon, but not PMMutil.exe, in the WPI 
installer. I get the same thing, when I try to build PMMail myself. I 
can manually build PMMutil.exe, in my DrDIALOG setup. The icon 
is static, and is simply placed in the \bin directory under version 
control.

After doing DOMAKE, PMMutil.exe should be in 
...\pmmdev\trunk\PMMail, but it is not, so there is no file to copy to 
\bin.

The Makefile in the PMMail directory has been updated between beta 1 and beta 2. The latest copy does copy PMMutil.EXE to the install\BIN directory when I make the install target.

The WIS file is checking a number of libraries that are now managed by RPM/YUM. It might be better to skip these checks and just list the libraries that PMMail needs so people can use ANPM or RPM/YUM to install them. I can make the changes and see if anything stops working. I think bogofilter, stunnel and tnef might be the external programs we still supply.

Neil

-- 
Neil Waldhauer  neil at blondeguy dot com  www.blondeguy dot com
Expert consulting for OS/2 Warp, ArcaOS and eComStation

--------------554FCE86BD815DB036F59135-- ----------- To unsubscribe yourself from this list, send the following message to MajorMajor at os2voice dot org unsubscribe PMMail2User end