Menu
▾
▴
#2680 Possible GPL violation: Binary snapshots only
We currently provide binary snapshots on the snapshots page:
http://sdcc.sourceforge.net/snap.php
While one could get corresponding source from the svn, I don't think that satisfies the requirement of section 3 of the GPL 2.
Maybe it would be enough to provide source snapshots (as we used to do in the past).
IMO a better alternative would be to have the source in the same snapshot archive as the binaries.
Philipp
On my local machine, using the instructions at http://sdcc.sourceforge.net/mediawiki/index.php/HOWTO_Make_Snapshot_Builds_on_the_Developer_Machine
doing a
~/build/sdcc-build-bootstrap.sh archive-src-trees 2>&1 | tee ~/build/log.txt
in the end, the source snapshots build fine. So getting the C++ 11 toolchain working on cf-86 should be sufficient to get back the source snapshots.
Philipp
Last edit: Philipp Klaus Krause 2017-11-02
I see no reason why the GPL would require the source to be in the same archive as the binary. How would you do that with code in an eeprom a PCB?
The only effect would be very large archives and possibly long and expensive downloads with contents most users would not need.
I am strongly against this idea.
Having the source included in the snapshot archves would ensure that we don't distribute binaries without having source snaoshots again.
However, when I suggested that I did not realize how big the SDCC source has become. For now, I agree that the archives would get too big. The situation might change when RFE #543 gets implemented.
Philipp
P.S. I think that even SVN access is enough to satisfy the GPL, but I still would like the source snapshots to be brought back.
We don't even need the C11++ toolchain to get this working. We just need to invoke ~/build/sdcc-build-bootstrap.sh archive-src-trees without crontab-spawn. I didn't make this change in time for today's snapshot, but I expect it to work tomorrow.
The source snapshots are back. I guess we can close this bug report now.
Philipp