Add explanation to blog post about snap/flatpak/appimage

[ronaldtse]

From @CAMOBAP

it's still not clear why exactly: "... you have to treat each distribution as another OS, further increasing the number of combinations"

I hope snap/flatpak/appimage should help us minimize such issues. The only problem which I remember sofar is glib link to specific version (runtime linker error)

Originally posted by @CAMOBAP in #4 (comment)

[maxirmx]

I was trying to say that if someone is deploying a complex Ruby application like metanorma in a traditional way (install Ruby, install gems, build extensions locally), each Linux distribution will require (slightly) different set of tools and libraries.
Firthermore, comapring different major versions of the same distribution (like Ubuntu 20 and Ubuntu 22) you may face different sets of tools and libraries.

Practically it means that you need to do at least testing on many versions and in terms of effort it is not very far from many different OSs. I believe rnp is another very good example how the testing effort and build complexity grows.

It is true that snap or appimage (or docker or tebako) help to minimize these issues.
I do not have detailed data to compare.

[ronaldtse]

The problem with various solutions:

• Snap cannot be run inside docker because it requires a daemon and file system mounting.

• Docker can only be run on machines with administrative access.

@CAMOBAP can you help describe how AppImage and Flatpak work?

[ronaldtse]

@maxirmx actually can you also help document how the Metanorma stack is built using packed-mn?

We should also create a simple gem with some dependencies in a new repository to serve as a sample; so we can include sample workflows etc for people to follow.

And we can blog about how packed-mn works, and also how to use the simpler approach.