Add an automated installer

[lphilmossb]

Currently, the installation process can be a bit hairy, particularly for inexperienced users. Thus I suggest we make a simple CLI install tool, where we at least get a local installation. We can even get fancy with letting the user select which packages to download, making sure possible dependencies are satisfied.

This should/could eventually be upgraded to a global installer, where the user either extends their texmf-path or supplies the location they usually store 3rd party packages, but this has low priority in comparison to local installation.

[lphilmossb]

After tinkering for a bit, it turns out (at least on Linux (probably MacOs as well, but I cannot test that)) that storing style files in ~/texmf/tex/latex automatically makes them visible to tex, so this should immensely simplify a global install. Maybe the end-user still needs to run texhash afterwards, but as it is in the user-directory, this should not even require root permissions.

[lphilmossb]

2ec54a9 introduces a first working version, which installs to ~/texmf/tex/latex, so at least on unix-based systems (at least linux), this should already constitute a user-based global install. Notice that this requires all users to install prettytex separately.

Currently, you can choose which branch to download from and which files to install. The plan is to introduce a caching system, where we create a separate cache directory (probably ~/.prettytex or ~/.cache/prettytex) and download files there. Then the user can separately say to make an install from the cache. Next to a global install, some local installs may be required. This should be simplified by this cache-approach as well, since we simply copy (or even link) the style files to the project folder. However, this idea still needs some design work.

[MrP01]

Thank you so much -- very nice!

The caching directory sounds good, even if it might not be strictly necessary - I'm happy with both.

[lphilmossb]

The idea for caching mainly stems from the fact that I do not know how Windows-users handle system-wide (or per-user) installations of packages outside of the MikTex console (which itself is a nice tool to be fair, but afaik only works with their upstream). Thus making lots of small copies per project seems the easiest to me. Storing files offline is only a premature precaution idea for the possibility if a user is not connected to the internet. However one could also just copy the files from a pre-existing project 🤷‍♀️ .