- currently, the .desktop calls the "boot-repair" executable, which calls the script that chooses the best "su" command (e.g. it will call "gksudo boot-repair"). Do you know a better way to implement it ?
How about creating an explicit boot-repair-wrapper script that chooses the best way to get root permissions?
As an additional precautionary action boot-repair itself could check if it has root permissons and exit otherwise. It would not try to get the permissions itself, however.
The desktop file would call boot-repair-wrapper.
If you are afraid someone might call boot-repair instead of boot-repair-wrapper because it has the nicer name, you might name them
boot-repair (for the wrapper script)
and boot-repair-backend or boot-repair-real (for the current boot-repair)
- currently, the .desktop calls the "boot-repair" executable, which calls the script that chooses the best "su" command (e.g. it will call "gksudo boot-repair"). Do you know a better way to implement it ?
How about creating an explicit boot-repair-wrapper script that chooses the best way to get root permissions? wrapper.
As an additional precautionary action boot-repair itself could check if it has root permissons and exit otherwise. It would not try to get the permissions itself, however.
The desktop file would call boot-repair-
If you are afraid someone might call boot-repair instead of boot-repair-wrapper because it has the nicer name, you might name them
boot-repair (for the wrapper script)
and boot-repair-backend or boot-repair-real (for the current boot-repair)
Just a suggestion.
Best Regards!