AppImage / AppImage/AppImageKit

Should an exec wrapper be used?

Offen
#396 23 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Keine Sprachdaten
Sterne
9.4k
Forks
588
PR-Merge-Kennzahlen
PR-Kennzahlen ausstehend

Beschreibung

So KDE AppImages are using these exec wrappers which are preloaded as libraries, right?
It took me a while to find the source code of it:
``` sh
git clone git://anongit.kde.org/scratch/brauch/appimage-exec-wrapper
```

There's an interesting comment in the source code about what this is actually meant for:
> Whenever your application invokes a child process through execv() or execve(),
this wrapper will intercept the call and see if the child process lies
outside of the bundled appdir. If it does, the wrapper will attempt to undo
any changes done to environment variables before launching the process,
since you probably did not intend to launch it with e.g. the LD_LIBRARY_PATH
you previously set for your application.

This sounds reasonable to me. Do you think this is something worth to implement your upstream binaries?

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.