On Sat, 9 Jul 2016 13:48:29 -0600 Tom Russo <ru...@bogodyn.org> wrote: > Github doesn't work like this. A release on github is just a tagged > state of the git repo, and when you ask to download it, it bundles up > that SHA-1 into a tarball/zipfile/whatever. You can't have it be a > processed version of the sources, like sourceforge does.
Actually, you can. Releases are created automatically by github when a tag is pushed to github. The release tars up the repository at that tag, but then you can edit the release page in github (describing the release in more detail than in the commit message with markup, if desired), and attaching arbitrary files, including binaries, to the release. See, for example, an executable jar we've uploaded to a release in another project I'm working on. https://github.com/kurator-org/kurator-akka/releases/tag/v0.3 -Paul -- Paul J. Morris Biodiversity Informatics Manager Museum of Comparative Zoölogy, Harvard University m...@morris.net AA3SD PGP public key available _______________________________________________ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
