On Thu, Jan 18, 2018 at 11:29:38PM +0000, Stuart Henderson wrote: > On 2018/01/18 18:40, Joerg Jung wrote: > > > > > > > Am 18.01.2018 um 14:31 schrieb Alexander Bluhm <alexander.bl...@gmx.net>: > > > > > >> On Tue, Jan 09, 2018 at 09:19:45PM +0100, Joerg Jung wrote: > > >> +SHA256 (blink1-1.98a.tar.gz) = > > >> sMsN8zlejocXA2OUII+tKCW9GmmAJCuULjKR6fv5DP4= > > >> +SIZE (blink1-1.98a.tar.gz) = 29503155 > > > > > > Github has recreated the tgz. Now I get > > > > > > SHA256 (blink1-1.98a.tar.gz) = > > > u0ZTJeCG2Ket9Y57Y+RcjggBSafnj1Y2KLFsxqCJTPE= > > > SIZE (blink1-1.98a.tar.gz) = 29503156 > > > > Uhhm... anyone an idea why they did this? > > Does this happen often? > > Sometimes it's due to an upstream commit on the tag. Sometimes it's due > to github upgrading something (these files are generated on-the-fly). > If you have old and new files around, diffing them might give clues. > > (I don't think I really want to know why the distfile is 28MB...)
Unfortunately, there is no distfile for the command line tool we build and install. The distfile just contains everything from their repo, various libraries for python, ruby, go, nodejs, java, ... GUI tools, Windows programs, and docs, etc.
