Attention : support for WAPT 1.8.2 ended on June the 30th 2022.
There are known vulnerabilities in WAPT dependencies in WAPT 1.8.2 branch. Please upgrade to the latest supported version. CVE listing (non exhaustive) :
When you create a template, there will be several files
in the folder .vscode inside your package folder:
settings.json;
launch.json;
Example with VLC:
wapt-get make-template "tis-vlc"
Using config file: /opt/wapt/wapt-get.ini
Template created. You can build the WAPT package by launching
/opt/wapt//wapt-get.py build-package /home/linuxuser/waptdev/tis-vlc-wapt
You can build and upload the WAPT package by launching
/opt/wapt//wapt-get.py build-upload /home/linuxuser/waptdev/tis-vlc-wapt
make changes to the setup.py file with an uninstall ;
defuninstall():apt_remove('vlc')
launch a remove from VSCode Run Configurations;
check that the software has been correctly removed
dpkg -l | grep vlc
Hint
In the uninstall() function, it is not possible to call for files
included inside the WAPT package. To call files from the package,
it is necessary to copy/ paste the files in a temporary directory
during package installation.
make changes to the setup.py file with an session-setup ;
In this example, you’ll need a vlcrc file in your package
to copy in home user. ensure_dir function and filecopyto
are from setuphelpers, the first one will test if the path exists,
the second one will copy your file from the WAPT package to its destination.
Once the installation and the de-installation are configured and tested
and the package is customized to your satisfaction, you may build and upload
your new WAPT package onto your WAPT repository.
If you have built packages on a different machine (ex: Windows
for building your Windows WAPT packages), you have to copy your .pem
and .crt keys on your Linux machine with WinSCP
or equivalent. Usually, this certificate bundle will be located
in C:\private on your Windows computer.
Then, provide the path to the certificates in /opt/wapt/wapt-get.ini.