How would the distro tell if the tar.gz is a program or just a bunch of compressed files? I tend to use tar files for compression rather than for distributing or installing software
Yes, but the header of the file says it’s a binary, that is why it gives you the option to run as a program or open as a file. Because the OS knows that you can do either with binaries.
Some file managers might add the +x automatically if you choose to run the binary through the desktop environment (not the terminal)… or ask you if you’d like to mark the file as an executable (i.e. add +x to permissions).
You can’t do it the same way with tar, what are you gonna execute, tar is neither a script or an ELF binary. It’s like asking for a zip file to be executable, doesn’t make sense. You can change the extension to .exe, but it won’t run, it’s not an exe, no MZ header, nothing 🤷.
How would the distro tell if the tar.gz is a program or just a bunch of compressed files? I tend to use tar files for compression rather than for distributing or installing software
By prompting the user to open as file / install as package
Like how many distros prompt (when opening executables) to open as file / run as a program
Yes, but the header of the file says it’s a binary, that is why it gives you the option to run as a program or open as a file. Because the OS knows that you can do either with binaries.
Is it the +x permission?
Why not use it the same way it is used in executables, but to indicate that a tar is installable
Some file managers might add the +x automatically if you choose to run the binary through the desktop environment (not the terminal)… or ask you if you’d like to mark the file as an executable (i.e. add +x to permissions).
You can’t do it the same way with tar, what are you gonna execute, tar is neither a script or an ELF binary. It’s like asking for a zip file to be executable, doesn’t make sense. You can change the extension to .exe, but it won’t run, it’s not an exe, no MZ header, nothing 🤷.