Info on *.WPI archives

PaulRS

unread,

Jun 16, 2017, 12:06:55 PM6/16/17

to

My basic question: Can I install a newer "gcc4core-1_3_1.wpi" OVER
the older "gcc4core-1_3_0.wpi" or does there need to be a an
"uninstall" THEN "install?"

What is the "rule" for this in *.wpi archives?

Paul
--

Andreas Schnellbacher

unread,

Jun 16, 2017, 1:07:01 PM6/16/17

to

(F'up set to c.o.o.misc.)

There can't exist a rule. WarpIN doesn't have a standard mechanism to
handle archive replacements. In some seldom cases (e.g. in NEPMD) the
script part of the installation includes a REXX macro that handles
updates. That REXX macro has to be configured manually for each
version by the package writer.

Therefore it's more recommendable to switch to RPM in your case.

A safe way is to always uninstall an old package before installing a
newer one. WarpIN in its current version can't do uninstallations
(via wic.exe) automatically. Actually the only way to achieve that
is a complicated method that Christian Langanke has decribed in has
presentation for WSE 2009
<http://wse2009.warpevents.eu/uploads/tx_wseevents/dev03.zip>.

--
Andreas Schnellbacher

Paul Ratcliffe

unread,

Jun 17, 2017, 11:01:00 AM6/17/17

to

On 16 Jun 2017 16:06:54 GMT, PaulRS <prs...@Zfrontier.com> wrote:

> My basic question: Can I install a newer "gcc4core-1_3_1.wpi" OVER
> the older "gcc4core-1_3_0.wpi"

Generally "yes". You'd certainly expect to be able to do so
for a minor version number change.
But some people are weird and do massive changes with nothing
to indicate such in the number.

> or does there need to be a an "uninstall" THEN "install?"

An uninstall/reinstall is always going to work but then you
might lose things you had subsequently set up e.g. shadows of
objects created by the package.

> What is the "rule" for this in *.wpi archives?

There isn't a "rule". It depends on what the packager author
decided.

PaulRS

unread,

Jun 19, 2017, 2:07:41 PM6/19/17

to

A General Thankyou!
Thanks to the anwers I just received
Thanks to those who tireless work on Foxfire for OS2
Thanks to those who keep up other OS2 stuff

I sucessfull installed Firefox 45 up from 31.8 using the info
supplied here and on the OS2 Mozilla page. From previous
installations I had to "neutralize" 8 earlier repeat files from
\ecs\dll. I have now made MOZSUPPORT a directory in the root
directory and put it in the LIBPATH (with its subs) This seems to
work well and may be helpful for future upgrades and searching out
repeat files. I did an uninstall-install on the GCC4 core.wpi library
as advised.

For those advising the *.rpm solution . . . I have worked with
OpenSuSe and the main issues is FINDING all the dependencies - I hope
OS2 development in this direction will put all dependencies in the
same spot and possibly be downloadable to ones own LOCAL repository
for reinstalls, etc as time goes by.

Again, Thanks to all!

Paul
--

Dave Yeo

unread,

Jun 21, 2017, 1:13:56 AM6/21/17

to

PaulRS wrote:
> For those advising the *.rpm solution . . . I have worked with
> OpenSuSe and the main issues is FINDING all the dependencies - I hope
> OS2 development in this direction will put all dependencies in the
> same spot and possibly be downloadable to ones own LOCAL repository
> for reinstalls, etc as time goes by.

So far there are only the netlabs and arcanoae repositories. They're
co-ordinated and the arcanoae one is pretty empty for now.
Personally, having a crappy connection, I wget most packages and put
them in my local repository
Dave