Repository navigation
Excludelist doesn't automatically update during runtime #286
Description
linuxdeploy doesn't automatically try to update the exludelist during runtime. This means that when using linuxdeploy, the latest excludelist is always the excludelist shipped with the used linuxdeploy 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 a tauri project to be updated, they need to wait on tauri being updated. For tauri to be updated, they need to wait on linuxdeploy being updated.) And it creates a single point of failure if there is no new linuxdeploy version after an excludelist update.
Therefore, linuxdeploy should also automatically try to update the excludelist at runtime.
Activity
TheAssassin commentedon Jul 24, 2024
Define "on build time".
At any rate, I'll create a new build to update the binaries.
TheAssassin commentedon Jul 24, 2024
Should be updated, please try https://github.com/linuxdeploy/linuxdeploy/releases.
[-]Excludelist doesn't automatically update during build time[/-][+]Excludelist doesn't automatically update during runtime[/+]Korne127 commentedon Jul 25, 2024
@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.But as it's the runtime of
linuxdeployitself, I changed the original wording.In any case, I just finished a pull request that implements this. It would be great if you could take a lot at it. :D