We should have an Installer release that matches the latest PeekabooAV release 2.1. So I went ahead and updated the docs and pstrap. While at it I improved consistency of repo references (to my mind at least) and fixed some typos.
What I'm wondering though: Even if we create a v2.1 tag, the installer will still install the latest PeekabooAV release from PyPI. (As does the v2.0 Installer release now there's a 2.1 on PyPI.)
Should we pin that as well, e.g. as peekabooav<2.2, so users always get the latest 2.1 point release? Or would we do matching point releases of the installer as well and pin to peekabooav==2.1?
We should have an Installer release that matches the latest PeekabooAV release 2.1. So I went ahead and updated the docs and pstrap. While at it I improved consistency of repo references (to my mind at least) and fixed some typos.
What I'm wondering though: Even if we create a v2.1 tag, the installer will still install the latest PeekabooAV release from PyPI. (As does the v2.0 Installer release now there's a 2.1 on PyPI.)
Should we pin that as well, e.g. as
peekabooav<2.2, so users always get the latest 2.1 point release? Or would we do matching point releases of the installer as well and pin topeekabooav==2.1?