I learned about WAPT from Korben's article (https://korben.info/wapt.html). As I was looking for an alternative to proprietary solutions, you came at just the right time!
Having been using it since version 1.0, it was time to give my feedback.
The problem I encountered perfectly matched WAPT's motivation: "to address the recurring issue of Flash and Java updates," while also being open source.
What a joy to find a solution that meets these criteria, and even more so when it's a French solution!
Since then, subsequent versions have been released, and for good reasons, notably regarding memory consumption and the package creation wizard.
Clearly, I like the software since I'm still using it today and plan to continue using it for many years to come, including for personal
use. Now for some suggestions:
1) Some custom-built packages are several hundred MB, even GB in size. Is it possible/planned to compress them during compilation? For example, by using a 7z library.
If an answer has already been provided in a previous post, please send me the URL; after searching, I haven't found anything.
2) I've noticed that the "C:\wapt\template" directory contains 'setup.py' templates for *.EXE, *.MSI, and even *.MSU (Microsoft Update Standalone Package) files used by some Windows updates, but not for *.CAB files.
As I also use WSUS Offline (and therefore *.MSU and *.CAB files), is a template planned for these?
Not seeing this function appear (and especially since I'm a complete beginner in Python), I'm working around this by using a very basic batch script to download and install these files from a network share, but it's a shame to resort to a makeshift solution when you have a proper deployment tool.
My final question
is: Is a PXE deployment solution planned? I'm gradually migrating to free and open-source French installations. I know there are already many alternatives to proprietary deployments; the question is, are you working on this? (Just curious.)
I wish you prosperity and a long life!
