Tranquil IT Forum

wapt 1.7.4,
Debian 9.6 server
, administration and package creation workstation under Windows 10.

Hello,

To handle package creation, I simplified things by creating a module script that I import right after setuphelpers.

During my local tests (before creating the package from the IDE), I had no problems.
Once the package is created, the installation goes smoothly, but uninstallation generates an error because my script is missing, even though it's part of the package.

Do you have any ideas?

Hello kcnarf,

kcnarf wrote: ↑Oct 21, 2019 - 4:58 PM wapt 1.7.4
Debian 9.6 server
, administration and package creation workstation under Windows 10.

Hello,

To handle package creation, I simplified things by creating a module script that I import right after setuphelpers.

During my local tests (before creating the package from the IDE), I had no problems.
Once the package is created, the installation goes smoothly, but the uninstallation generates an error because my script is missing, even though it's part of the package.

Do you have any ideas?

After installation, the WAPT package is not kept on the machine as is, otherwise it would use too much space. The setup.py file is extracted and stored in the SQLite database within the WAPT directory. If you have added another file, it will no longer be present at the time of uninstallation or session_setup. The only way to prevent this is to store it by integrating the functions into setup.py or copying your library file to a location that will be available at the time of uninstallation.

Sincerely,

Denis

THANKS !