Re: [Hamlib-developer] modified distfile with hamlib 4.5 release (possible security issue)

[Greg T. <gd...@le...>]

Sorry for the false alarm.   Apaprently I saw

> https://github.com/Hamlib/Hamlib/releases/tag/4.5

and just edited the tag into a github-fetching macro, which fetched the
auto-generated repo tarball, rather than the actual release.  github
seems to encourage not having release files, and used to, I think, make
it difficult, so I've gotten used to projects not making distfiles and
instead using automated source tarballs.

It would still be nice to clarify in README the github/sourceforge
relationship and if it's expected that the set of files in sourceforge
for a release is identical to those on github (except that github also
provides repo tarballs, which are missing on sourceforge as they aren't
actually release files).

73 de n1dam