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.