Tranquil IT Forum

Hello,

Is it possible to prevent a package from being cached on the client PC, and
instead only have the script executed there? I have several large packages (the largest is 6 GB) and I'd like to link them to certain PCs that already have the software installed (before the WAPT agent was set up). Therefore, I'd like to avoid the WAPT agent downloading all the packages from the server, then running the script, and simply detecting that the software is already installed. If I'm not mistaken, the package is first downloaded to the client PC (as a .WAPT file) and then decompressed. This means that 12 GB of free space is wasted in the end. And I think some of our client PCs don't have that much free space on their hard drives.

Is there a solution to get around this problem?

Best regards,
Christophe.

Hello Christophe0110,

Christophe0110 wrote: ↑Jul 18, 2019 - 3:08 PM Is it possible to prevent a package from being cached on the client PC, and instead have the script executed on it?
I have several large packages (6 GB for the largest) and I'd like to link them to certain PCs that already have the software installed (before the WAPT agent was set up). Therefore, I'd like to avoid the WAPT agent downloading all the packages from the server, then running the script, and simply detecting that the software is already installed. If I'm not mistaken, the package is first downloaded to the client PC (as a .WAPT file) and then decompressed. This means that 12 GB of free space is wasted in the end. And I think some of our client PCs don't have that much free space on their hard drives.

Is there a solution to get around this problem?

For large packages like this one, it's possible to separate the data file from the configuration package. In your configuration package, you can check if the software is already installed, and if not, force the installation from within setup.py using WAPT.install('xxx-mypackage').

This can be convenient, but you have to keep in mind the limitations of this type of operation, which are that the dependency is not clearly displayed (in the control file), and that consequently, you have to be sure that there will still be a network when the package is installed, because it will not have been cached beforehand (because waptagent cannot anticipate that it will need it).

Sincerely,

Denis Cardon