Page 1 of 1
Problem with package update functionality
Published: February 4, 2021 - 10:58 AM
by t.heroult
Wapt: 1.8.2 (Linux)
Infrastructure: Windows 10
Hello,
I'm having trouble managing updates in the packages I create.
When I modify a package, it reinstalls on client machines.
I've tried making changes in the "update-package" section, but they're not being applied.
My question is:
How can I make it so that updating a package version triggers an update and not a new installation?
Thanks in advance!
Tom
Re: Problem with package update functionality
Published: February 5, 2021 - 10:25 AM
by dcardon
We need to be more specific about the problem you're experiencing... Most software updates itself by running the installer, which detects the existing installation and updates it. A WAPT agent will download and install a new package if it has a version number. The `update_package()` function is only useful for updating the package itself, not for updating workstations.
Re: Problem with package update functionality
Published: February 5, 2021 - 10:49 AM
by t.heroult
Hello.
In my case, I typically have a package with folders containing files (executables and others), as well as PowerShell code.
When I update my package with new files, I don't want it to go through the entire installation process again, but just perform the updates.
However, I have the impression that I need to manually configure the "install" function to determine if the files are already installed or not.
If that's the case, it's really unfortunate that the agent can't tell the package: "This is an update, not an install..."
I find this quite strange coming from a system that relies so heavily on version numbers.
Re: Problem with package update functionality
Published: February 11, 2021 - 1:49 PM
by dcardon
Hello,
there are so many different scenarios that it would be difficult to automatically guess what the system administrator wants. SetupHelpers provide a whole suite of tools to easily manage this in a deterministic way. Personally, as a system administrator, I prefer deterministic behavior to a flawed pseudo-AI algorithm that tries to guess what I want to do...
If you're thinking of a .deb system, WAPT's operation is quite different because of the subject matter. Most of the time, we package installers, not individual files, unlike a .deb package.
Sincerely,
Denis
Re: Problem with package update functionality
Published: February 14, 2021 - 1:31 PM
by vcardon
Hello,
have you considered separating your software from the data you want to pass to it?
The two can be different WAPT packages with their own lifecycles, with your data package becoming a dependency for your software.
The documentation might give you some ideas.
Re: Problem with package update functionality
Published: February 16, 2021 - 4:16 PM
by t.heroult
Hi Vincent
, yes, it's possible, but I'd rather avoid having multiple packages.
In the meantime, I've modified the installer to check certain things; depending on the results, it will either perform an installation or an update.
Thanks anyway.
