On approximately 1/1/2004 3:27 PM, came the following characters from the keyboard of Morbus Iff:
I deleted a bunch of discussion I couldn't follow the logic of...
Here is what I want:
# as per your thoughts: use $TEMP/par-$USER-EXEID, and # clean up the existing files inside at BEGIN/END. pp -o AmphetaDesk.exe AmphetaDesk.pl
# as per your thoughts: use $TEMP/par-$PID, and # clean up the existing files inside at BEGIN/END. pp -o AmphetaDesk.exe -cleartemp AmphetaDesk.pl
It is not clear to me why par-$USER-EXEID would be used sometimes, and par-$PID would be used sometimes. Seems like the latter is more unique over time, if a single user can run multiple copies of the same par .exe file.
# where-ever the .exe ends up, assume a data/internal # directory exists. if it doesn't, create it automatically. # no cleaning at BEGIN/END. pp -o AmphetaDesk.exe -temp data/internal AmphetaDesk.pl
# where-ever the .exe ends up, assume a data/internal # directory exists. if it doesn't, create it automatically. # since "cleartemp" is set, we cleanup at BEGIN/END. pp -o AmphetaDesk.exe -temp data/internal -cleartemp AmphetaDesk.pl
Since the options are to pp, they'd be internal to the .exe, not dependent on anything from the environment (save $TEMP and $USER, where needed).
At runtime, no $ENV: $TEMP/par-$USER-$EXEID, clean at BEGIN/END.
At runtime, $PAR_TEMP: use that directory, no cleaning.
At runtime, $PAR_CLEARTEMP: use $TEMP/par-$PID, clean at BEGIN/END.
At runtime, $PAR_TEMP/CLEARTEMP: use that directory, clean at BEGIN/END.
Other than the above comment, the set of desired functionality sounds practical to me, even though I didn't understand the discussion leading up to it.
-- Glenn -- http://nevcal.com/ =========================== The best part about procrastination is that you are never bored, because you have all kinds of things that you should be doing.
