Sat Jun 13 06:44:03 2020: Request 132811 was acted upon.
Transaction: Correspondence added by ralf.neuba...@wido.bv.aok.de
Queue: PAR-Packer
Subject: RE: [rt.cpan.org #132811] Win32: Crash a week after start
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: ralf.neuba...@wido.bv.aok.de
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=132811 >
Hi.
> > FWIW, I'd be OK if the default PAR_TEMP location was in the user's
> > home dir or under C:\ProgramData ($ENV{PROGRAMDATA}). The latter
> > might have issues on shared machines depending on how the unpacked
> > files are used, though.
>
> $ENV{APPDATA} would be better than $ENV{PROGRAMDATA}
>
> It is easy enough to add to mktmpdir.c for Windows builds, so I can work up a
> PR if Roderich is in favour of the idea.
What is your concept for getting rid of old PAR_TEMP locations once you get (or
create) an updated version of the application or just stop using it? Explicit
deinstallation (maybe by using a special argument or variable when calling this
version)? An own version of 'delete old files' but with a longer timeout and
using a better protocol for detecting the last use and removing only whole
directories? Giving the user better hints than cryptic directory names with
cryptic files in it, that he can decide which dirs to purge manually? This
could be implemented by description files or by a version manager.
Explicit deinstallation could be paired with explicit installation -- the
application only unpacks intelf into a permanent location, if you explicely
tell it to do so, in a way every user understands.
Mit freundlichen Grüßen
Ralf Neubauer
