On Tuesday 23 June 2009, Rick Altherr wrote: > Technically, nothing is required from the project-side. The > infringement happens solely at the time of distribution, not at the > time of authoring or compilation. Since OpenOCD is only released as > source code, the project is not directly affected by any > infringement.
I actually saw an "msi" file on the Berlios download page. Which I believe is one flavor of MS-Windows installer. > Doing nothing still leaves packagers and distributors > open to the possibility of committing infringement rather easily, but > that is still a choice made by them, not us. D2xx is by default > disabled. _If_ we choose to do anything for 0.2.0, it could be as > simple as adding a warning that by having D2xx enabled, the resulting > binaries cannot be distributed. That sounds like it's worth doing ... one could do more later too. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
