How would you have to rewrite the script to make it automatic?
For "sudo" the rule already exists, now a rule for "su" has to be created.
So no matter how the user installs the program, it is always installed correctly and executable - without having to rewrite the installer_script. sh manually.
Example: I had installed Renoise with "su" and I could start it without any problems as a user. To uninstall it I switch to the "/home/foo/bar/Renoise" directory and run "Renoise # ./uninstaller. sh" script.
I also had "su" installed on Mixbus (Bitwig,...?) and I could start it without problems as a user. It installed itself in the "/opt" directory. To uninstall it I switch to the "/opt/Mixbus" directory and run "Mixbus # ./uninstaller. sh" script.
Fall down, maybe. any other inconsistencies in the script? Elieser, the developer ("... let's see if somebody in the linux forum can help. My linux skills are just the minimum") would be grateful to you IMHO.
I guess it's up to the user. I you have sudo, you do "sudo ./install.sh", if you don't have sudo, you simply use "su" and run the script afterwards as root.
# emerge -1av libpng
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] media-libs/libpng-1.6.32:0/16::gentoo USE="apng (-neon) -static-libs" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Would you like to merge these packages? [Yes/No] no