• Info on *.WPI archives

    From PaulRS@21:1/5 to All on Fri Jun 16 16:06:54 2017
    XPost: comp.os.os2.misc

    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
    --

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Schnellbacher@21:1/5 to PaulRS on Fri Jun 16 19:06:59 2017
    XPost: comp.os.os2.misc

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

    On 16.06.17 18:06, PaulRS wrote:

    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?

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Ratcliffe@21:1/5 to PaulRS on Sat Jun 17 14:46:19 2017
    XPost: comp.os.os2.misc

    On 16 Jun 2017 16:06:54 GMT, PaulRS <prschmi@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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From PaulRS@21:1/5 to All on Mon Jun 19 18:07:40 2017
    XPost: comp.os.os2.misc

    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
    --

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave Yeo@21:1/5 to PaulRS on Tue Jun 20 22:14:22 2017
    XPost: comp.os.os2.misc

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)