2

GPLv2 requires, when redistributing modified version of the source code, to notify in the source files the date of change.

But what about removing source files? Is there any requirements of notifying a file is removed from the source? What about things like makefile?

Finally - what about adding new source files? Does it suffice to state in the file the date on which the source file is added, and a copyright notice?

1
  • For the last part, please consider reading "How to Apply These Terms to Your New Programs" at the end of the licenses (both GPLv2 and GPLv3). You can adapt the suggestions of GPLv3 to use it with a GPLv2-only codebase as well (as long as you keep the same license as required).
    – Brandin
    Nov 21, 2023 at 13:20

1 Answer 1

2

You need to notify the recipients of changes being made.

Think of a person - like you - who discovers a new repository which solves some issue you have or which is a cool project. Where do you look what it does, what changed and who works on it? You usually go first to

  • the readme file
  • the changelog file
  • the license file
  • the copying file

Usually the whole repository is covered by one license - thus it also includes the instructions for the build system like Makefile etc. If several licenses cover different files, the readme or license or copying file is also a good place to indicate that (additional to any header in the files themselves).

Further, it's good practise to summarize changes made in the readme or changelog file. That solves at the same time the issue that removed files cannot carry any changed headers due to their absence. Thus removal is easily indicated also like

Cleanup / Update: removed long out-dated port to OS/2 and updated build system for x86 to work with newer versions of gcc and clamp.

As to adding new files: Yes, it's good to add a header to them with project name, license indication and copyright statement - but it's not a requirement either. The important thing is, that recipients are clear under which license and under whose copyright a file falls. Thus I'd do both and also add it to the readme, changelog or copying file of the project indicating that you made changes (and roughly which).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.