Just Download the new application file.

[ritishbhardwaj]

I want to just download the new .exe file from the server and do not want to overwrite it on the the place of older .exe .
The function download_and_apply_update is also updating the older .exe.
Can you explain me how can i do it gracefully
Also i tried get_targetinfo(target_path: str | [TargetMeta])→ TargetFile | None but unable to understand what is this TargetMeta and from where to get it....

[ritishbhardwaj]

I have tried some experiments, like

            target_filename = any_update.target_path_str

            target_path = os.path.join(meta_dir, target_filename)
            print(f"Target path to get info: {target_path}")

            mytrinfo= client.get_targetinfo(target_path=target_filename)
            test_return=  client.download_target(targetinfo=mytrinfo)

and this is successfully downloading, but the file which is getting downloading is .tar.gz file, which i don't want.
I want the functionality within the tufup which , same like download_and_apply_updates(), will extract the .exe file and placed in settings.INSTALL_DIR and then remove the .tar.gz from the targets directory of the Client side repo directory.

[dennisvang]

... and this is successfully downloading, but the file which is getting downloading is .tar.gz file, which i don't want. ...

The .tar.gz archive is extracted to a temporary directory in the Client._apply_updates() step, right before calling the install function mentioned in my answer to your previous question.

To change what happens with the extracted files, you have two options:

• specify a custom install function: Anything you want to do with the extracted archive can be specified in a custom install function, which can be passed into Client.download_and_apply_update(), as explained in the example here. The install function is platform dependent, so, as a starting point for a custom install function on Windows, you could copy the default _install_update_win() and modify that as necessary.

• specify a custom batch_template: Depending on your specific needs, you could specify a custom Windows batch template, as explained in the example here (either in stead of, or in addition to a custom install function).

Basically, on Windows, the default install function opens a new process to run the steps from the batch template, then closes the app so that its files can be replaced. The default batch template does a copy/overwrite using robocopy. You can modify this to meet your needs.

Note that much of the complexity of the windows install function and batch template comes from the fact that windows does not allow overwriting a running executable. However, if you are not overwriting the running .exe, then you may not need to use a separate process with a batch template at all. In that case you could just specify a highly simplified install function very similar to the Mac version.