Afaik this is not possible currently, but there is an easy workaround. You can build the installer with pdeploy, extract the files, and then re-create your modified installer with NSIS (which is the tool invoked by pdeploy).
Thanks for the tip yaio, I’ll give it a try. I don’t have experience with nsi scripts but it is a nice thing to learn.
I’ve tried a “dirty” modification to the Installer class of DeploymentTools.py (located at direct/p3d folder). But when I run “python pdeploy.py” I got an error, I mean even without changing anything.
Running “python pdeploy.py” should be the same as runnig pdeploy.exe? If I cound run pdeploy.py I think I can quickly do the modifications in DeploymentTools.py to fit my needs.
Yep, I obtained errors if I tried launching pdeploy as a python script, I asked and they said that pdeploy isn’t supposed to be executed that way. I don’t know it there is an easier way, but I recompiled Panda, obtaining a working version of customized pdeploy.