In this case, what about just combining the two packages? Is there any benefit to having two separate packages? Obviously there's at least one downside.
In the thread were I showed my codesigning package, there was the legit remark that codesigning certificates do not come for free, so many developers do not use them.
The installer engines my other package supports (InnoSetup, NSIS, WiX Toolkit) are all free, so could of interest to more users.
Since they're primarily for my own use, I could of course just combine them, but since I also want to share and have the code public on gitlab, I'm trying to think on how to make this "good"
I've now implemented the third-package method from taazz.
@SkyKhan: wow! That's what I was looking for when I started this thread!
Slow is not really a problem here, since building the installer takes many seconds, signing it takes many seconds also, so a few milliseconds more in the one call leading from one to the other is of no relevance
Your example shows a new object here, but I guess it's pretty much the same with class functions that would give me the existing singleton instance
Many thanks for the input from everyone here, this helped me solve this pretty fast!