- Sponsor
-
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
RFE: --tempdironhome
← creating random temporary directory on user home
#302
Comments
Believe it or not, early on Makeself was used as part of installers of games from CDROM so this is not exactly a new use case. The easier workaround for this is just to set the |
I didn't claim that installing from СDROM is a new use case for makeself. I described a scenario when
If makeself would setup itself environment variables (like $TMPDIR) before running extract/installation, this can be solution for the case (build time option like |
I understand, but I'm also not clear that this is a decision that can necessarily be made on behalf of the user at the time of the archive's creation. Who's to say which directory will fit? If we can't trust /tmp or similar, then why should we assume the home directory (for instance) does not not have any such limitations either, or is otherwise unsuited? |
Theoretically, I agreed.
Something like In our case we know about target linux systems that…
This use case coud be common for case with big archives from CDROM (does not fit to /tmp and cannot unpack to subdir). And practically, for all these cases, a heuristic like "if we cannot unpack in the current directory, let's unpack to $HOME" with 99.99% probability will be enough. |
This is easily worked around by the user performing the extraction:
|
@belonesox time to name names. Which distros? If I wanted to reproduce, then can I use a docker image to do so? |
Many Linux distributions use tmpfs for the /tmp directory by default, as tmpfs provides a fast and efficient way to manage temporary files, but unfortunately loosing xattr attributes, and limited on size by default. Some examples of Linux distributions that use tmpfs for
Actually, I even dont know modern Linux, where installer does not use
Without extra tuning of On next comment I will show how "reproduce losing xattr on tmpfs". (I was thinking that the problems about limitations of default /tmp on tmpfs is well known and obvious) |
@belonesox My situation (on Ubuntu Focal) is different than yours:
|
Statements like this one make me feel as though the next issue you file will be against I'm against (further) complicating the implementation of Adding yet another option to |
About demo, how to loose xattrs on tmpfs (if your are using modern linux with /tmp on /tmpfs). Unpack:
|
Yes, many old LTS Linuxes did not use tmpfs for tmp, and you definitely run custom LVM partitioning. Hmm, I cannot get — how should I prove, that modern linuxes using tmpfs by default? By linking to modern mainstream installers source code? |
Of course, I would like to not use even less ugly workaround like
(Why users should know anything about variables/options, if it not necessary) |
I am trying (probably unsuccessfully) to convince, that this case is not very specific («big on tmpfs from CD»)
Yes, it is ugly heuristic. :( I will try to think about better solution, and will be glad to see better ideas. |
Because implementing this functionality is costly --- in development, certainly, but mostly in test units. Putting aside the question of whether this functionality should exist, how do you propose to unit test it? Would you use |
Let's consider the following use case:
So,
--notemp
)--notemp
(because impossible to unpacking to subdirectory of readonly CDROM)Implementing something like
--tempdironhome
(creating random temporary directory on user home) can be a solution.Also, this can solve issue #300.
May other solutions exist.
The text was updated successfully, but these errors were encountered: