[wpkg-users] /forceinstall option does not seem to work

[Bernhard Mayr]

> Are you certain that /forceinstall is working as designed?

I'm absolutely NOT certain that /forceinstall is working as you assumed
from the documentation. I just wanted to say that I would have assumed what
you assumed, had I tried to do what you are trying to do.


> I'm resistant to making another revision to force an upgrade, as often
the changes are quite small and frequent

Everyone should do what works for them, but frequent small changes are
exactly what makes it cumbersome to keep track of, and that's where for me
versions come in handy. I frequently define a version number as a variable
in packages and use them in the package revision and install string.

<package id="FFox_x86ESR" revision="%version%.%pkg-revision%" name="Mozilla
Firefox ESR x86" reboot="false" priority="10">
    <variable name="version" value="68.11.0" />
    <variable name="pkg-revision" value="1" />
...
    <install cmd='"%SOFTWARE%\FFox\Firefox Setup %version%esr.exe" -ms' />
'''
</package>

This way I can prepare the updated version as an installer file or
directory with a new version number and once I'm ready to deploy I just
update the version number in the package. For quick and dirty hacks like
little scripts I just use the version scheme YYMMDD e.e. 200803 for today's
date. I think this is how wpkg is meant to work and in this case I'm
certain that it works as expected.

good luck

Bernhard



Am So., 2. Aug. 2020 um 23:57 Uhr schrieb Luke Whitehorn <
luke.whitehorn at gmail.com>:

> Hi Bernhard,
> I'm resistant to making another revision to force an upgrade, as often the
> changes are quite small and frequent -  it's a Python library and
> supporting files that I'm deploying.
> I'd rather not use execute="always", as I'd prefer to keep updates of this
> controlled by me.
>
> Are you certain that /forceinstall is working as designed? From the docs
> on that page it states for /forceinstall: 'The "install" command will be
> run, even if "check" conditions are met.'
> The install command is simply not being run :/
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_-1142062398511601272_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Sun, 2 Aug 2020 at 19:50, Bernhard Mayr <bmmayr at gmail.com> wrote:
>
>> Hi Luke,
>>
>> from what the page on wpkg.js flags (https://wpkg.org/WPKG_flags) says,
>> I would assume that it works as you expected. However this page is for a
>> previous version of wpkg.js flags and it also says:
>>
>> *"A better way is to increase a package revision for a single package
>> (the one you know is broken), and make an "upgrade" of that single
>> package."*
>>
>> That is exactly what I do in those cases, when I just want to run an
>> install again, without actually changing anything and it works quite well.
>> In these cases I also omit any check conditions and use execute="once"
>> and it will only run when I increase the package revision.
>>
>> If an install doesn't take many resources and doesn't minded being
>> installed all over again frequently you can also use execute="always" (
>> https://wpkg.org/Execute_once_/_always)
>>
>>
>> Am So., 2. Aug. 2020 um 11:01 Uhr schrieb Luke Whitehorn <
>> luke.whitehorn at gmail.com>:
>> >
>> > Hi all,
>> > I've been trying to crack this one for a while now, but with no luck.
>> > It should be simple; I have a package installed, and I just want WPKG
>> to run the install again. Ignore checks, just run it again.
>> > It seems like the /forceinstall flag should do this, but it just isn't
>> working.
>> > I am running the following command (and multiple similar variants):
>> > cscript.exe
>> \\192.168.15.130\projects\__SharedAssets\__Software_Install\WPKG\wpkg\wpkg.js
>> /force /forceinstall /install:"nymus-client" /nonotify
>> >
>> > Which gives me this output:
>> > Package 'Nymus Client' (nymus-client): Already installed.
>> Re-installation enforced.
>> > Package 'Nymus Client' (nymus-client): Already installed (checks
>> succeeded). Checking dependencies and chained packages.
>> > Package 'Nymus Client' (nymus-client): Package and all dependencies are
>> already installed. Skipping.
>> > Package 'Nymus Client' (nymus-client): Package and all chained packages
>> are already installed. Skipping.
>> >
>> > Why is it skipping after saying 'Re-installation enforced'? Why wont it
>> just install?
>> >
>> > Virus-free. www.avast.com
>> > ---------------------------------
>> > wpkg-users mailing list archives >>
>> http://lists.wpkg.org/pipermail/wpkg-users/
>> > _______________________________________________
>> > wpkg-users mailing list
>> > wpkg-users at lists.wpkg.org
>> > https://lists.wpkg.org/mailman/listinfo/wpkg-users
>> ---------------------------------
>> wpkg-users mailing list archives >>
>> http://lists.wpkg.org/pipermail/wpkg-users/
>> _______________________________________________
>> wpkg-users mailing list
>> wpkg-users at lists.wpkg.org
>> https://lists.wpkg.org/mailman/listinfo/wpkg-users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20200803/d767a399/attachment.html>