Kenneth Ölwing wrote:
>  I have a fairly large perlapped application that I distribute 
>  internally. A hundred or more users, [...] many with .so/.dll files, 
 >  so they need to be unpacked while in use [but] I don't want [temp dirs]
 >  littering the common servers for all eternity.

I may have been part of that discussion a few years ago.  The subsequent
resulting improvements to specifying a lib directory *relative* to the
directory from which the .exe was run obviated the need for perlapp to 
to create any temp files at all, and solved the problem for me.

Of course, then you have the problem of having to distribute your app 
with a real installer (like PerlMSI, Nullsoft or Innosetup) that can 
install all the perl libraries in a subdirectory right *next* to your 
app, instead of just passing around a single monolithic runnable 
compiled perlapp binary that has to spew all those files somewhere onto 
the filesystem at runtime.

hope this helps,

-dave
_______________________________________________
PDK mailing list
PDK@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs