What release artefacts should we build?

[stephengaito]

I would like to open a discussion about what release artefacts we should build as well as who or how we might go about regularly building them.

For each build artefact we should provide arguments for (or against) regularly building the artefact.

Of primary importance is the easy of use for both the end user as well as the pdf2htmlEX release team

You can see the list of currently proposed release artefacts and thier associated discussion in the pdf2htmlEX Build Artefacts Project Board

[stephengaito]

Over the past couple of days I have spent considerable time learning about the different alternative release formats: AppImage (#2), Docker (#5), Snap, Flatpack and Homebrew (#6).

This is my attempt to both make it easier for others to use pdf2htmlEX as well as reduce the "release load".

At the moment, I think we should be building an AppImage, a Debian package, maintain the Homebrew/Linuxbrew formulae (which can also be used by TravisCI) and possibly maintain the Docker file (but not build/relase docker images).

I have created issues in the pdf2htmlEX/buildAndPackagingTools project in order to allow more detailed discussion of each option.

It is VERY important that we all realise we have limited time/resources with which to build/maintain any objects we might decide to maintain.... if you are passionate about an object.... be prepared to explain how you will help keep it uptodate!