I'm responsible for the creation of the Strawberry Perl distribution ( http://strawberryperl.com/ ) and for three months during 2008 I was funded by the Perl Foundation to natively implement Portability into Perl.
I'm happy to report that (a few beta bugs notwithstanding) it was a complete success. But now I've got a bit of a problem when it comes to doing the portableapps.com packaging...
We have deep support in the Perl binary now and the CPAN client, and even the regular File::HomeDir->my_document style APIs natively report portableapps.com-compatible paths when they detect they are running in a portable context.
We even have a beta of a zip-packaged Portable Perl distribution being automatically spat out of the distribution build scripts (http://strawberryperl.com/download/strawberry-perl-18.104.22.168-portable-bet...).
My problem now, unusually, is how the hell do I build the ACTUAL portableapps.com package out of the .zip file directly?
This is a slightly unusual build (compared to what seems to be the normal process) in that I just need 100% of all the existing files, unmodified, with no registry hacks or changes of any kind, and I can't find any obvious documentation on taking this direct unmodified path to an installer.
Everything I can find to read seems to be based around converting existing non-Portable applications over into Portable form...
Got any pointers or URLs on how to go from .zip to NSI installer direct?