Well, sort of. I need a solution that is portable across Solaris, Linux, Windows, MacOSX, HP-UX, etc. with minimal fuss.
A pp app gives me portability and simplicity of installation (i.e. no installation required). The user can simply copy the binaries anywhere they like and it just works. I don't mind requiring an installer for server components, but anything that requires extra installation steps for every user of the system is an impediment to user adoption. Batch files and vbscripts are problematic if you are using cygwin instead of cmd as the shell. To get it all working on Windows would require that I create and maintain a .bat file that calls a .vbs file, plus a shell script for cygwin and unix users, plus the original .pl file and all its supporting files. This is doable and would certainly resolve the space and performance concerns, but it's a lot more complicated than the self-contained binary approach. >From a supportability standpoint pp does pretty much exactly what I want, ignoring the performance and disk space issues we've been discussing. --Scott -----Original Message----- From: Roderich Schupp [mailto:[EMAIL PROTECTED] [...] Now I think I understand what you really want: (1) a mechanism to determine everything that's used by your application (2) arrange all this stuff below some given directory (3) have it work when started from there even when the given directory has been moved around [...] -
