Steve Madere wrote: >Have any of you developed a strategy to >package an application using Tcl::Tk >for deployment? > >
I do Tcl::Tk application packaging in two different strategies. First one, which works without temporaries, is indeed based on Tcl::Tk (where all unzips is performed in memory w/o disk) This results in about 4 files, and right now i have no intentiions to do single-file executable this way. My second approach uses PAR for single-file executables, I apply this when it is allowed to do unzipping into $TEMP. >If it was all just Perl code and shared >libraries, I assume I would use PAR. > >Is there some kind of extension or adapter >to PAR which will also package up all of >the required Tcl modules? > > > Unfortunately currently PAR is unable to package Tcl::Tk, mostly because it makes false positives as it guesses presence of Perl/Tk. My local copy of Module::ScanDeps is free of this problem, but I doubt that my modifications will go to the official module. But removing perl/Tk logic from Module::ScanDeps is enough for Tcl::Tk to be processed correctly. That said, I am probably the only user of PAR+Tcl::Tk combination, and this size of user base isn't enough for promoting the approach. Vadim.
