|Claudio Luck 158b714450||10 months ago|
|.Setup||12 months ago|
|contrib||11 months ago|
|docs/screenshots||12 months ago|
|locale||10 months ago|
|parts||10 months ago|
|plat||10 months ago|
|src||10 months ago|
|webstart||12 months ago|
|.drone.yml||10 months ago|
|.gitignore||11 months ago|
|.gitmodules||11 months ago|
|BUILDING.txt||12 months ago|
|GNUmakefile||10 months ago|
|README.md||12 months ago|
|pEp_Thunderbird_Setup.desktop||10 months ago|
This is a component of the pEp Installer for Linux (it does not consistute a useable installer on it's own). This is the program to launch from a *.desktop file, which in turn will offer user choices, and then run backend scripts with proper privileges.
It also has the facility to prompt the user for an administrative password shall the backend script prompt accordingly on its stdout (pseudo-terminal) or stderr.
The uninstall button is only exposed if launched with the option
git clone https://gitea.pep.foundation/claudio/pEpLinuxSetupForThunderbird.git git submodule update --init make - or - make wx_config=/path/to/custom/wx-config
./tb_setup -h ./tb_setup -U /path/to/pEp_Thunderbird_Setup.desktop
The ./tb_binary execution is meant to be wrapped by a *.desktop file carrying specific parameters for the installation. Two ways of launching tb_setup exist, (a) by means of the Exec= setting, and (b) by means of a shell "shebang" while the .desktop files executable bit is also set. In the latter case, tb_setup relies on the shell passing the .desktop file as the script to be executed as an argument to the running interpreter, which in this case is tb_setup. To achieve symmetry between the two modes of launching, the .desktop file shall be structured as follows:
#!/usr/bin/env ./tb_setup # # [ Text that explains to the user on how to start # this as a script from the console. ] # [Desktop Entry] Exec=sh -c './tb_setup "%k"'
Whenever tb_setup is launched this way, it will parse the .desktop file and extract installation parameters. It will then set defaults and launch install scripts according to the parameters.
[Desktop Entry] X-pEp-Exec= X-pEp-Import-Exec= X-pEp-MDA-Version= X-pEp-MDA-Platform= X-pEp-MDA-OS= X-pEp-MDA-Variant= X-pEp-Prefer-User-Install=yes|1|no|0
The options and values are case sensitive.
The X-pEp-Exec is a file path to the script performing the adapter installation. It is called with the command line arguments and with appropriate privileges (root or user) as described below. The X-pEp-Import-Exec is called after the adapter installation, and called with the command line argumentsas described below, while it is always called as the current user. The values of X-pEp-MDA-Version, X-pEp-MDA-Platform, X-pEp-MDA-OS and X-pEp-MDA-Variant are passed through to the install scripts.
If not set explicitely, X-pEp-MDA-Variant defaults to
tb for system installs,
tbmini for user installs.
mkdir -p tmpbin ln -sf /bin/su tmpbin/su PATH=$PWD/tmpbin ./tb_setup -U