On 2018/05/10 16:14, Wes Hardaker via Net-snmp-coders wrote: > 6. downloads > > Github uses a different mechanism for distributing tarballs of > downloads. But I don't see an issue with this in the future.
One thing to note with this that's not immediately obvious with github downloads, the automatically added "source code" links in github releases are generated on-the-fly then cached, so they're subject to change if they update software on nodes if the files expire from cache. If this occurs it causes issues for distro packagers that check hashes, or for anyone checking pgp signatures. There's a way to upload an "asset" with a release on github allowing a stable tar file to be uploaded and attached to it; rather than rewrite one of my old list posts about this here's a link, https://www.conserver.com/pipermail/users/2018-March/msg00006.html I wish github would document this better! ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
