-
-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
«--notemp» does not recreate «new directory created in the current directory» but unpack all files to old directory with same name #300
Comments
This exactly and diametrically opposite to how I assume |
Sorry, I missed, I mean "… we expect that if the |
Ah. That makes more sense. How about something like this? |
Wow! Exactly that! Thank you for quick fix! |
Happy to help! 😁 |
On documentation we see
«
--notemp : The generated archive will not extract the files to a temporary directory, but in a new directory created in the current directory. This is better to distribute software packages that may extract and compile by themselves (i.e. launch the compilation through the embedded script).
»
Consider that directory named «out».
If the directory named
out
already exists, we expect that if the--nooverwrite
tag is not used, the oldout
directory will be deleted and the content will be unpacked to a new, cleanout
directory.What we have now («makeself-2.4.5») is that makeself unpacks content to the subdirectory
out
, overwriting existing files, but keeping old files (which may remain from previous installations, for example), thus tainting the installation process.We're not sure if this is a bug or a feature, but we don't see a way to get a clean
out
directory while unpacking. The--cleanup
option is available, but it's not reliable and doesn't guarantee that theout
directory will always be clean or absent.The text was updated successfully, but these errors were encountered: