On Wed, 10 Jan 2007 21:02:45 +0100, Kenneth Ölwing <[EMAIL PROTECTED]> wrote:
>Hmm, ok - that might work, but for ActivePerl I'd use the AS style package; >problem is the PDK. > >Are there similar options for the PDK msi, and if so what are they more in >detail? Can I be sure that an msi installed in that manner won't mess up any >existing settings in the registry (e.g. if I happen to have PDK 7 installed >already)? Will it leave uninstall information behind (considering that the >unpacking of it would be basically a transient thing, and when I'm done I'd >just wipe the directory where it was installed. Etc... > >Failing all the above, is it possible to just scavenge a 'real' PDK >installation and zip up the whole or part of the tree? If I can just take >bits and pieces what would be essential (considering just PerlApp)? Seems to >me the PDK install is pretty benign so this might be the easiest route >perhaps... Yes, you can just ZIP up the PDK install directory and prune it to the files you need. For PerlApp on Unix this is probably just bin/perlapp lib/pdkcheck-5.x For PerlApp on Windows you need bin/perlapp.exe bin/lib/pdkcheck.exe bin/lib/pdklib.dll bin/lib/perl58.dll You should be able to move the files anywhere as long as you keep the lib directory at bin/../lib on Unix and at bin/lib on Windows. You will also need to install the PDK license on your build machine under your build account. Cheers, -Jan _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
