Skip to content

Allow using extract-and-run via environment variable#953

Merged
TheAssassin merged 1 commit into
masterfrom
extract-and-run-env-var
May 1, 2019
Merged

Allow using extract-and-run via environment variable#953
TheAssassin merged 1 commit into
masterfrom
extract-and-run-env-var

Conversation

@TheAssassin

Copy link
Copy Markdown
Member

Useful for "nested" AppImage calls, e.g., linuxdeploy plugins called
by linuxdeploy in a Docker environment.

Useful for "nested" AppImage calls, e.g., linuxdeploy plugins called
by linuxdeploy in a Docker environment.
@TheAssassin TheAssassin merged commit effcebc into master May 1, 2019
@TheAssassin TheAssassin deleted the extract-and-run-env-var branch May 1, 2019 21:00
@probonopd

Copy link
Copy Markdown
Member

Maybe export the env when the AppImage is invoked with --appimage-extract-and-run?

@TheAssassin

TheAssassin commented May 2, 2019

Copy link
Copy Markdown
Member Author

Not sure what you mean... You mean, so that applications know that it's an extracted run? I'd rather do the opposite and would hide that fact. AppImages shall never rely on such a "feature", they shouldn't try to edit the contents even when it's possible due to the extraction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants