On 18 October 2015 at 18:06, Dirk Hohndel <[email protected]> wrote: >> >> i don't think this makes much sense for the Windows installer, so >> that's not really a portable solution. >> then again, i have no idea how zsync works... > > But remember, Lubomir - we are only talking about AppImages for Linux. > Nothing will change for Windows.
discussion went a bit off topic for a hypothetical peace of software. i did add: >>>> how would you approach this silly big CAD software example in a >>>> portable OS manner? > >> ideally: >> - as the author of the huge CAD software i would write a update method >> that works on all platforms (e.g. with Qt - HTML download with local >> file replacement) >> - AppImage would be the way to distribute the package on Linux >> - if the user wants to update the CAD software on a regular basis >> he/she can do an AppImage --install and delete the original AppImage. >> - once the AppImage is installed, it's now part of a RW filesystem and >> the above update method works without a problem. >> - no third party tools in the process and no browsers...the user just >> starts a small "updater" GUI app which downloads the huge CAD software >> packages. >> - this is how the Android SDK is managed on Windows; not sure about other >> OSes. > > I think you are putting requirements on AppImage that are beyond what > is needed at this stage. > > Yes, the question of granular updates will be asked at some point, but > today when I update the Windows binary that's an 80MB download and > I have heard zero complaints about that... Yes, this would be different > for a 2GB download. But I hope Subsurface never grows to that size. > certainly, i'm really making this more of a discussion about the future of AppImage as a deployment method as i like what it does. should have added an <offtopic> somewhere in the posts... lubomir -- _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
