Add --exclude-library option to standalone version#178
Add --exclude-library option to standalone version#178TheAssassin merged 1 commit intolinuxdeploy:masterfrom
Conversation
ee732b7 to
a1cd6fc
Compare
|
We should use an environment variable, which then is usable both in standalone and plugin mode. Please see https://github.com/linuxdeploy/linuxdeploy/wiki/Plugin-system#controlling-plugin-behavior. |
|
@TheAssassin I added the env var please look at linuxdeploy repo this is for the stand alone mode only |
|
I'm not sure I quite understand you here. An environment implemented in linuxdeploy only has no effect in plugins at all unless they support them, too. Usually, it is preferable, though, to implement a specific one for the plugin. It's really low effort to |
|
I'm talking about linuxdeploy/linuxdeploy#283 |
a1cd6fc to
324d734
Compare
324d734 to
ac8d266
Compare
|
Hello, what's the status of this PR? @TheAssassin? |
|
Can this be merged? This is a problem everytime I'm trying to use linuxdeploy |
|
while this is not merged you can either build it or use the files from my fork https://github.com/dantti/linuxdeploy-plugin-qt/releases/tag/continuous |
ac8d266 to
f17765b
Compare
f17765b to
08c6159
Compare
|
Is there any update on this? |
It would be useful to have the standalone version also able to exclude-libraries, this helps with issues: linuxdeploy#153 linuxdeploy#150 linuxdeploy#110 linuxdeploy#108
08c6159 to
5f78fb0
Compare
It would be useful to have the standalone version also able to exclude-libraries, this helps with issues:
#153
#150
#110
#108