Stas Sergeev

> and can archive for eternity with ease. Unfortunately not, for licensing concerns. Archiving dosemu2 with proprietary game will not allow publications and archiving. Referring to another appimage is probably...

> I don't think the game flatpak contains much except the game and the metadata. > I think they use an overlay filesystem, at runtime the games filesystem is overlaid...

As far as I understand, even if I am allowed to distribute the game with some non-free license, I can have problems distributing dosemu2 with it in a same appimage....

Ok, thanks, I checked gpl and made sure that aggregating indeed does not matter.

So in this case maybe someone wants to write an appimage-based scripting prototype? :) It of course doesnt mean flatpack-based prototype is unneeded! We need to find out what is...

Or more realistically, we just need to support both methods. Which one is better, is not even a valid question in an absense of an obvious limitations.

@stuaxo what a chicken-out? :) If everyone is right, then we need both methods. But I realize having a reason to not write a prototype, is a good thing to...

https://github.com/briceburg/docker-dosemu2/blob/master/Dockerfile-build-alpine Does this help? Not sure how actual is that though. @bricebug @volkertb could you please help with short instructions for alpine?

https://github.com/briceburg/docker-dosemu2/blob/master/Dockerfile-build-alpine Does this help? Not sure how actual is that though. @briceburg @volkertb could you please help with short instructions for alpine?

There is also the problem that `searpc-signature.h` produces `-Wstrict-prototypes` warnings because of missing `void` in function prototypes. But it seems you don't have issue tracker enabled, where I could report...