|
|
Log in / Subscribe / Register

The "preferred form" issue

The "preferred form" issue

Posted Aug 4, 2011 7:10 UTC (Thu) by JoeBuck (guest, #2330)
Parent article: Emacs and the GPL

Perhaps it's time to audit distros, looking for C code that came out of specialized preprocessors that are not included and that winds up linked with GPL code.

The "preferred form" issue also comes up when people license non-software works under the GPL. If you distribute an image under the GPL, and you created it with the Gimp, no one can pass it on if you didn't include the preferred form for making modifications; if you save your work in XCF, that's the "source" (likewise for Photoshop users it's the PSD). If you distribute music, and you produced it by mixing, again you haven't provided the preferred form (so your recipients can remix it). If it's a document, you can't just include a PDF, that isn't the source. The preferred form is the form that you, the author, preferred (perhaps you like LaTeX, or maybe LibreOffice).


to post comments

The "preferred form" issue

Posted Aug 4, 2011 14:43 UTC (Thu) by nix (subscriber, #2304) [Link]

Perhaps it's time to audit distros, looking for C code that came out of specialized preprocessors that are not included and that winds up linked with GPL code.
Of course that wouldn't have spotted this problem, which is elisp code which came out of a specialized preprocessor and was not linked with anything, but *is* itself licensed under the GPL.

The "preferred form" issue

Posted Aug 5, 2011 17:06 UTC (Fri) by hummassa (guest, #307) [Link]

$ grep "preferred form" debian-l-index | wc -l
1232338473763 lines
$ :D

The GPL does not say to whom the "preferred form" is to be preferred...


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds