Roderich Schupp wrote: > Sounds like a bug in PAR to me: the whole purpose of the > /tmp/par-USER/cache-SHA1/... files is to only extract stuff > on the very first run of a PAR packed executable. Later invocations > are not supposed to extract the stuff again when they see that > the cache directory already exists. > > Cheers, Roderich
Mmm... there might be more than one problem here. Not only does the shared library keep getting re-extracted, it also seems as if the permissions of the included library is not preserved. The "running program" error can be avoided if the library is used with no permissions for others, since this has the effect of localising the shared library to the executing user. (I'm not sure if this is specific to AIX). So the copy I included had "0750" permissions but still ends up in the cache with permissions based on the current user's umask. By now I've also installed Archive::Unzip::Burst under AIX (wow was that painful) in the hope it would handle things differently, but this does not help - the shared library always seems to gets extracted using Archive::Zip... The error does however disappear if I set my umask to "027" when running the packed binary for the first time or manually change the permission of the library in the cache to 0750. Should I log a bug? cheers Niel
