Skip to content
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

RFE: Options like «--target» for makeself to specify default unpack directory #306

Closed
belonesox opened this issue May 10, 2023 · 2 comments

Comments

@belonesox
Copy link
Contributor

belonesox commented May 10, 2023

Currently, users can specify the installation directory for a self-extracting archive using the '--target' option. However, there is no way to specify the default unpack directory, only the option to unpack to a temporary directory or not (see also the discussion on #302).

It would be great if we could specify the directory to which the archive should be unpacked. Many use cases involve unpacking the content from the .sh file to '/opt/mysoft' or '~/apps/mysoft' and running a post-install script without copying from a temporary or proxy directory, thus saving time and space (and solving lot of problems with loosing extra attributes or correct rights because of incorrect umask, etc).

For me it will be good workaround for #302 :)

@belonesox
Copy link
Contributor Author

belonesox commented May 10, 2023

There is some workaround — it possible to pass to makeself something like

--notemp  --untar-extra "-C /opt/mysoft "

but makeself "did not know" about unpacking to /opt/mysoft and trying to create subdirectory (and it will be empty) in current dir
(that lead to fail then running self extracting script on read-only file systems, like CDROMs).

@belonesox
Copy link
Contributor Author

Oww.

Looking at code of makeself I discovered that this option already exists!

But missed in section "Usage" of https://makeself.io/ .
Looks like the documentation should be fixed.

belonesox added a commit to belonesox/makeself that referenced this issue May 15, 2023
megastep pushed a commit that referenced this issue May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants