On 10 Jul 2004 at 16:36, Dean Arnold wrote:
> the.noonings wrote:
> > A note of caution.
> >
> > Let us suppose that the user has more than one application that has been
> > built by par. The top level cache directory, $ENV{TEMP} plus "\par-$USER",
> > holds a \cache-" plus the SHA1 hash of the executable for each. Attempting
> > to remove the said entire top level cache dir in the uninstall routine of
> > one would remove the caches of the others, too. Not desirable. We need to
> > delete only the cache for the application which we are trying to delete.
> >
> > No, I don't know how to do that.
> >
>
> I'm not certain I understand the issue you're raising.
> Is it that (while only remotely possible) multiple, different
> applications could generate the same SHA1 hash ?
>
Malcolm was warning about trying to rmdir the "par-$USER" parent dir, in the case
where it also contains a "cache-xxx" for another PAR exe. There is no way to know if
the other dirs are currently in use by running programs. Your technique does not do
that, so it's OK.
"pp -C" or PAR_GLOBAL_CLEAN, by comparison, will also remove the "par-$USER" dir, if
after removing its own "temp-$PID" dir, the "par-$USER" dir is empty, making it just a
bit cleaner. No traces of PAR left, if all PAR exe's are -C.
That's not possible if some PAR's are cached, so you may have empty "par-$USER" dirs
left laying around.
Alan Stewart
