Those sources can be found in the various make files. They typically specify a URL for a tar, zip, or other archive file, or a repository and version to retrieve. All the information of "what and where" is in the OpenWRT code, or the build system wouldn't work. It's just not "easily digestible" to get a full list and the information about licensing. While there is a field for it in the package Makefile's metadata, isn't reliably populated.
And here are the archives:
Just need to find if there is a file somewhere that links all the archives used by each release
I find the legal aspects about this very interesting, however I doubt anyone buying this device will make any problems (within the 3 years specified above) for a second (third hand) device that has an average selling price of $20 on eBay (refurbished condition).
As for flashing back to OEM, I think your selling point is actually that is has OpenWRT pre-installed. Still a lot of people are afraid to flash devices themselves, but would love to try third party firmware.
1 Like
Just point people to https://github.com/openwrt/openwrt/releases/tag/v18.06.0 or another appropriate tag. At no point the GPLv2 states that you need to provide a file like that. It says:
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
The preferred form of work to modify OpenWrt is using the OpenWrt buildroot which you can obtain in .tar.gz form from the github releases page, though one could argue that pointing users to a specific Git tag for cloning it themselves is sufficient.
All source code archives which are built by the buildbots while assembling images are cached on http://sources.openwrt.org/ so users can obtain the unmodified archives from there in case upstream ever goes away.
1 Like
I thing you are right but ... There could by a "spy" from CISCO/Meraki using this to avoid difusion of OpenWrt devices having a negative impact on their business!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.