-
Notifications
You must be signed in to change notification settings - Fork 85
Excludelist doesn't automatically update during runtime #286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Define "on build time". At any rate, I'll create a new build to update the binaries. |
Should be updated, please try https://github.com/linuxdeploy/linuxdeploy/releases. |
@TheAssassin Build time was probably not the best term to use as it's very ambiguous. I meant the "build time" / packaging time of the AppImages as it's usually the build time of the projects that use |
linuxdeploy
doesn't automatically try to update the exludelist during runtime. This means that when usinglinuxdeploy
, the latest excludelist is always the excludelist shipped with the usedlinuxdeploy
version.This is problematic as it requires a new
linuxdeploy
version to be shipped and downloaded / used by everyone in order for excludelist changes to take effect. This also means that updates have to "trickle down" as you can see in AppImageCommunity/pkg2appimage#555: (For atauri
project to be updated, they need to wait ontauri
being updated. For tauri to be updated, they need to wait onlinuxdeploy
being updated.) And it creates a single point of failure if there is no newlinuxdeploy
version after an excludelist update.Therefore,
linuxdeploy
should also automatically try to update the excludelist at runtime.The text was updated successfully, but these errors were encountered: