Make proper source releases without binaries

[rhertzog]

Free software projects tend to provide source tarballs to make it easy to distribute the software at known points of the history. With github you can easily do that just by creating a tag of the version that you want to release. eg "1.0", "1.1", etc.

It would be nice if you could start doing that as I had to invent a version for heartleech when I packaged it for Kali Linux.

I also noticed that you provide ready-to use binaries in the "bin" sub-directory. Those should not be part of such "source releases" and should ideally be moved to some other place (another git repository if you want).

Thank you!

[robertdavidgraham]

I marked the current release as "1.0.0i". This change includes some better command-line help, a better manpage, and removal of the PCRE linking.

I should remove the kali32/kali64 images, but I have decided about how I'm going to solve the win32/mac issue, where users are less likely to be able to download things themselves. I think I'll just create a "binaries" project under github and upload all my tools there.

[jhbruhn]

I know, this is a rather old project, but you also have the ability too add binaries (or any other file) to those github-releases. This might be handy if you ever want to publish binary releases.