2 ms·
The linking aspect is only a line in the sand where fsf will enforce the license, and is not part of the license text. To my knowledge it comes from the idea th
by belorn 10y ago
The linking aspect is only a line in the sand where fsf will enforce the license, and is not part of the license text. To my knowledge it comes from the idea that binaries with linked libraries will generally not work without those libraries and that that dependency is a strong indicator that we are dealing with a single work rather than multiple independent and separate works.
In contrast to uncertainty, I think we can be quite certain that django works without mysql (I personally run several sites with postgresql). Modules for django would likely not work without django, so they are likely derivative of django and not the other way around. I also vaguely recall fsf stating that they don't consider the linking guidelines to be that relevant for software written in languages without linking, which would include python programs.
Is your problem with the license that FSF as an organization has an opinion on how derivate works can be identified for software?
- ubernostrum 10y agoIs your problem with the license that FSF as an organization has an opinion on how derivate works can be identified for software? My problem is that the FSF's opinion on what constitutes a derivative work is horribly broad, and has never to my knowledge been tested in court. So despite all the reasonable intuitive opinions in the world, who knows?