Home/ Questions/Q 7774929
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T17:30:06+00:00

It is generally considered good practice to add some lines with author, version and

  • 0

It is generally considered good practice to add some lines with author, version and license information to the top of source files. For instance, Gnu GPL v3 suggests to add

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year>  <name of author>

This program is free software: you can redistribute it and/or modify
it under the terms [SNIP]

I find it tedious to add it manually to each file, and to have to update them all every now and then when some of this information changes (new authors, copyright years, version bumps).

Is there a way to manage this automatically, so that I only have to edit this stuff in one place and it gets automagically copied around?

If needed, you may assume that I am using any modern revision control system.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It is generally considered good practice to add some lines with author, version and license information to the top of source files.

    That depends. First of all there are two (and more) ways to do this:

    • manage licensing information per file
    • manage licensing information in a central location

    If you start a project from scratch, the per-file method is often easy to do while keeping things clear. As you write, over time it becomes more difficult to keep track of things. So more and more projects switch to the central location variant.

    The file-by-file method has the benefit that the scope of a work is clear. Often you write the name of the application in the file-comment. If a single file is taken out for some reason, the information is still in there and the documentation chain is not broken.

    With the central location method, the benefit is that this is normally supported by your version control software, for example GIT. Commits can be signed by the committing person, and author can be given. It’s documented who has written which code automatically and that information is stored in a central location: the VCS.

    Keep a COPYING file with your package where you provide the main information centrally. You can easily generate the list of authors via the VCS. And per each file you can create one header that just specifies which software and where to look into, just a bare outline:

    /**
 * Flux Deluxe v3.2.0 - Vector Drawing Redefined
 *
 * Copyright 2010, 2012 by its authors. 
 * Some rights reserved. See COPYING, AUTHORS.
 */

    If you release a new version in a new year it’s a no-brainer to update all files.

    • 0