Copyleft/guide Changeset - ed42a7eba575

Changeset - ed42a7eba575

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 10 years ago 2014-03-20 10:41:07
bkuhn@ebb.org

This text on Installation Information is a description of GPLv3§6,
not of GPLv3§2.

1 file changed with 17 insertions and 16 deletions:

gpl-lgpl.tex

0 comments (0 inline, 0 general)

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
 tutorial) handle that issue.  (Early drafts of GPLv3 included those
 requirements in the definition of CCS; however, given that the lock-down
 issue only comes up in distribution of object code, it is more logical to
 place those requirements with the parts of GPLv3 dealing directly with object
 code distribution).
 % FIXME: this goes somewhere else
 In Draft 3 we instead use a definition of ``Installation Information'' in
 section 6 that is as simple and clear as that goal.  Installation Information
 is information that is ``required to install and execute modified versions of
 a covered work \dots from a modified version of its Corresponding Source,''
 in the same User Product for which the covered work is conveyed.  We provide
 guidance concerning how much information must be provided: it ``must suffice
 to ensure that the continued functioning of the modified object code is in no
 case prevented or interfered with solely because modification has been
 made.''  For example, the information provided would be insufficient if it
 enabled a modified version to run only in a disabled fashion, solely because
 of the fact of modification (regardless of the actual nature of the
 modification).  The information need not consist of cryptographic keys;
 Installation Information may be ``any methods, procedures, authorization
 keys, or other information.''
 % FIXME: Standard Interface
 % FIXME: System Libraries: it's in a different place and changed in later drafts
 The final paragraph of section 1 revises the exception to the source code
@@ ... @@
 section 6.  In Draft 3 we made clear that the requirement to provide
 Installation Information implies no requirement to provide warranty or
 support for a work that has been modified or installed on a User
 Product.  The Final Draft adds that there is similarly no requirement to
 provide warranty or support for the User Product itself.
 % FIXME: this needs integration
 In Draft 3 we instead use a definition of ``Installation Information'' in
 section 6 that is as simple and clear as that goal.  Installation Information
 is information that is ``required to install and execute modified versions of
 a covered work \dots from a modified version of its Corresponding Source,''
 in the same User Product for which the covered work is conveyed.  We provide
 guidance concerning how much information must be provided: it ``must suffice
 to ensure that the continued functioning of the modified object code is in no
 case prevented or interfered with solely because modification has been
 made.''  For example, the information provided would be insufficient if it
 enabled a modified version to run only in a disabled fashion, solely because
 of the fact of modification (regardless of the actual nature of the
 modification).  The information need not consist of cryptographic keys;
 Installation Information may be ``any methods, procedures, authorization
 keys, or other information.''
 %FIXME: This probably needs work to be brought into clarity with tutorial,
 %next three paragarphs.
 Why do distributors only have to provide Installation Information for User
 Products?

0 comments (0 inline, 0 general)