This is essentially a repaeat of #425 but for different reasons.
AppImages of a newer spec allow the use of a portable mode that allows you create a <Appimage_Name>.config directory for storing files. Currently, the Appimage dumps files (a cache folder, cookies.jar, settings.json) in whatever directory it's located in, and although I can create the .config folder and enable portable mode, it doesn't actually respect that and drops files in the same directory.
This was rejected before because you didn't like the submitter wanting to run it containerized. In my case, this is a problem because I like to update my AppImages with Gear Lever, which is useful for this this project especially as it is prone to frequent unscheduled updates with a preview build being the only working copy. Gear Lever manages updates for you, but it does so by moving every AppImage into a managed folder, such as ~/AppImages. The typical managed folder just has nothing but .AppImage files in it. While TDM can be run this way, it doesn't behave like a good citizen, polluting the managed folder with it's dependencies, cache, and config.
So I'm requesting this because I'd like to create a config folder for the app, keep all the dependent files in there, and manage updates of the AppImage itself with the same tool I use to keep others up to date. Currently TDM requires me to come check GitHub manually.
This is essentially a repaeat of #425 but for different reasons.
AppImages of a newer spec allow the use of a portable mode that allows you create a <Appimage_Name>.config directory for storing files. Currently, the Appimage dumps files (a cache folder, cookies.jar, settings.json) in whatever directory it's located in, and although I can create the .config folder and enable portable mode, it doesn't actually respect that and drops files in the same directory.
This was rejected before because you didn't like the submitter wanting to run it containerized. In my case, this is a problem because I like to update my AppImages with Gear Lever, which is useful for this this project especially as it is prone to frequent unscheduled updates with a preview build being the only working copy. Gear Lever manages updates for you, but it does so by moving every AppImage into a managed folder, such as ~/AppImages. The typical managed folder just has nothing but .AppImage files in it. While TDM can be run this way, it doesn't behave like a good citizen, polluting the managed folder with it's dependencies, cache, and config.
So I'm requesting this because I'd like to create a config folder for the app, keep all the dependent files in there, and manage updates of the AppImage itself with the same tool I use to keep others up to date. Currently TDM requires me to come check GitHub manually.