AppImage / AppImage/AppImageKit

Should an exec wrapper be used?

Abierto
#396 23 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Sin datos de lenguaje
Estrellas
9.4k
Forks
588
Métricas de merge de PR
Métricas de PR pendientes

Descripción

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?

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.